Weave
Sign InSign Up
View as .md ↗
Google Search Console

Google Search Console | Get Performance Overview

MCP server · Marketing · google.com · 4 categories · 10 tools

Powered by Advanced GSC ↗

Google Search Console is Google's free tool for tracking how your sites perform in Google Search. This integration lets your AI workflows read that data — search traffic and rankings, index coverage and URL inspection, and sitemap status — for the properties your connected Google account can access.

gsc_get-performance-overview

Fetch a high-level search performance summary for a Search Console property over a date range — either a rolling window (days) or an explicit startDate/endDate pair. Data typically lags live traffic by about 2 days. Read-only.

Tool Input

siteUrlstringrequired— The Search Console property, exactly as it appears in Search Console — either an absolute URL-prefix property (e.g. https://www.example.com/, including any trailing slash) or a domain property (sc-domain:example.com). Forwarded verbatim, never normalized; use gsc_list-properties to see the connected account's exact property identifiers. If the connected Google account cannot verify this property, the partner returns no data rather than an error.(min length: 1)
daysinteger— How many days of data to fetch, counting back from today. Mutually exclusive with startDate/endDate. Omit all three for the partner's default window.(>= 1, <= 90)
startDatestring(date)— Start of the date range (YYYY-MM-DD). Must be provided together with endDate; mutually exclusive with days.(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$)
endDatestring(date)— End of the date range (YYYY-MM-DD). Must be provided together with startDate.(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$)

Tool Output

siteUrlstringrequired— The Search Console property.
startDatestring— Start of the reporting window (YYYY-MM-DD).
endDatestring— End of the reporting window (YYYY-MM-DD).
totalsobjectrequired— Aggregated totals across the whole window.
clicksnumber— Total clicks.
impressionsnumber— Total impressions.
ctrnumber— Click-through rate (clicks ÷ impressions).
positionnumber— Average position in search results.
dailyarrayrequired— Per-day performance rows.
[]object
datestringrequired— The day (YYYY-MM-DD).
clicksnumber— Total clicks.
impressionsnumber— Total impressions.
ctrnumber— Click-through rate (clicks ÷ impressions).
positionnumber— Average position in search results.

We're Adding More Google Search Console Tools Constantly!

Don't see a specific Google Search Console tool you need? Email [email protected] and we can add it.

Google Search Console Frequently Asked Questions

What does the Get Performance Overview tool do?

This page documents the Get Performance Overview tool (gsc_get-performance-overview). Fetch a high-level search performance summary for a Search Console property over a date range, either a rolling window (days) or an explicit startDate/endDate pair. Data typically lags live traffic by about 2 days. Read-only. It is one of the Google Search Console Search Analytics tools, invoked through your firm's Weave MCP connection and available to members whose access level permits it.

Can I use both days and an explicit date range?

No, days and startDate/endDate are mutually exclusive, and startDate/endDate must be provided together. Omit all three for the partner's default window.

What is the Google Search Console integration?

The Google Search Console integration connects your firm's Google Search Console account to Weave. Google Search Console is Google's free tool for tracking how your sites perform in Google Search. This integration lets your AI workflows read that data, search traffic and rankings, index coverage and URL inspection, and sitemap status, for the properties your connected Google account can access. It groups 10 tools into 4 categories, exposed through your firm's Weave MCP connection and filtered per member by access level.

How does my firm connect Google Search Console to Weave?

An admin authorizes a Google account with access to your Search Console properties once, via Google's OAuth consent flow in the Weave console. Every firm member then works through that single connection, there is no per-member Google sign-in.

Why did a tool return no data for our site?

Every gsc tool that takes a siteUrl requires the connected Google account to be a verified owner or user of that property in Search Console, if it can't verify the property, the tool returns no data rather than an error. gsc_list-properties is the exception: it takes no input and simply lists every property the connected account can access, so start there to get the right siteUrl.

Why does the data look a couple of days behind our live traffic?

Search Console's performance data typically lags live traffic by about two days; that's a Google-side reporting delay, not a Weave sync issue.

Can these tools change anything in Search Console?

No. Every gsc tool is read-only, none of them can submit URLs, edit sitemaps, or change any Search Console setting.

Related Tools

compare-search-periodsget-advanced-search-analyticslist-properties