Google Search Console by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

gsc query search analytics

gsc_query_search_analytics

Read-onlyIdempotent

Query Google Search Console Search Analytics to retrieve clicks, impressions, CTR, and average position by query, page, country, device, date, or search appearance.

Instructions

Query Google Search Console Search Analytics. Returns clicks, impressions, CTR, and average position for queries, pages, countries, devices, dates, and search appearances. Use gsc://metrics, gsc://dimensions, gsc://filters, and gsc://compatibility for available fields and rules.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`filters`	No	Filters combined according to this tool's query schema. Use provider field names and the declared operators.
`metrics`	No	Native: clicks, impressions, ctr, position. Calculated: ctrOpportunity, clicksPerImpression, impressionShare, clickShare.
`orderBy`	No	Field used to order report rows.	clicks
`siteUrl`	No	Search Console property URL, e.g. https://example.com/ or sc-domain:example.com. Uses GSC_SITE_URL when omitted.
`startRow`	No	Optional 0-based row offset for explicit pagination.
`dataState`	No	final=stable data, all=fresh daily data, hourly_all=fresh hourly data (use hour dimension).	all
`dateRange`	No	Explicit reporting start and end dates in YYYY-MM-DD format.
`datePreset`	No	Named reporting period. Use the custom date range when you need exact start and end dates.	last28days
`dimensions`	No	Up to 5 dimensions selected from query, page, country, device, date, hour, searchAppearance.
`searchType`	No	Search surface to report, such as web, image, video, news or Discover. Availability depends on the property.	web
`autoPaginate`	No	When true, omit rowLimit so the GSC client auto-paginates until exhaustion.
`orderDirection`	No	Sort direction for the selected ordering field.	DESC
`aggregationType`	No	Official GSC aggregation. byProperty is incompatible with page grouping/filtering and Discover/Google News. byNewsShowcasePanel requires discover/googleNews plus searchAppearance equals NEWS_SHOWCASE, and forbids page grouping/filtering or another searchAppearance filter.	auto

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / dateRange / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / filters / items / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / startRow / maximum
```
Added value: +9007199254740991
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds the metric set it returns, but says nothing about GSC row caps, quota/rate-limit behavior, or how autoPaginate interacts with limit, all of which matter semantically for this call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and the return shape, with the discovery pointer last. No filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 14 parameters, nested filter objects, and an output schema, the short description is defensible because the schema is fully documented and return values are covered by the output schema. The one real gap is guidance on dimension/metric compatibility, which is deferred entirely to the gsc:// resources rather than summarized.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including bounds, defaults, enum meanings, and the aggregationType compatibility constraints, so the schema carries the burden. The description adds no parameter-level meaning beyond redirecting to the gsc:// resources, which is the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (query Google Search Console Search Analytics) and enumerates the returned metrics and supported breakdown dimensions, so an agent knows exactly what data it gets. It does not name any sibling to contrast with (e.g. gsc_find_losses_gains or gsc_compare_search_types), so differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage direction is a pointer to gsc://metrics, gsc://dimensions, gsc://filters, and gsc://compatibility for valid fields and compatibility rules, which is genuinely useful for a tool with 6 enums and cross-field constraints. There is no statement of when to choose this tool over the many analysis siblings, and no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.