Google Search Console by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

gsc query search analytics

gsc_query_search_analytics

Read-onlyIdempotent

Retrieve Google Search Console search analytics data—clicks, impressions, CTR, and position—filtered by queries, pages, countries, devices, dates, and search appearances.

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

TableJSON 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

TableJSON 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.

First observedv2.0.1Sep 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that it returns clicks, impressions, CTR, and position across several dimensions, which is useful but largely overlaps with the output schema. It does not disclose additional behavioral traits such as rate limits, data freshness handling, or pagination behavior beyond what the schema already specifies.

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 core purpose and return data, followed by a terse pointer to supporting resources. Every word earns its place; no filler or redundancy.

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

Completeness3/5

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

The tool is complex (14 parameters, nested objects, many enums), but the input schema covers parameter details at 100% and an output schema exists, so the description need not explain those. The pointer to compatibility rules is valuable, yet the description omits any summary of the critical constraint that dimensions are limited to 5 or the aggregationType incompatibilities—though these are in the schema. Given the schema richness, the description is adequate but not comprehensive, especially without guidance on how this raw query relates to sibling analysis tools.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaningful guidance by pointing to gsc://metrics, gsc://dimensions, gsc://filters, and gsc://compatibility for available fields and rules, which helps the agent construct valid metric/dimension/filter values beyond the raw schema. This extra pointer lifts the score above baseline.

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?

The description states a specific verb ('Query'), resource ('Google Search Console Search Analytics'), and return metrics/dimensions, making its core purpose clear. However, it does not explicitly contrast itself with sibling analysis tools like gsc_find_losses_gains or gsc_cluster_queries, so it earns a 4 rather than a 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It only points to gsc:// metrics, dimensions, filters, and compatibility resources for field rules, which is operational guidance, not tool-selection guidance. With 18 siblings performing higher-level analyses, the absence of any 'use this for raw data, use X for analysis' note is a clear gap.

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