Google Search Console MCP Server

Overview Schema Source Related Servers Discussions Admin

Query Discover performance

query_discover_analytics

Read-only

Fetch Google Discover analytics: clicks, impressions, and CTR by page, country, or date. Filter by search appearance; no query or device data.

Instructions

Google Discover performance: clicks, impressions and CTR by page, country or date. Discover reports no queries, no average position and no device breakdown, and has data only for sites that appear in Discover feeds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filters`	No	Filters, combined with AND.
`end_date`	No	Last day (inclusive), YYYY-MM-DD in Pacific Time. Defaults to today.
`site_url`	Yes	The property, as listed by list_sites: 'sc-domain:example.com' for a domain property or 'https://www.example.com/' for a URL-prefix property. A bare domain such as 'example.com', or any URL on the site, is resolved to the property that contains it.
`row_limit`	No	Rows to return (1-25,000).
`start_row`	No	Zero-based row offset, for paging.
`data_state`	No	'all' includes fresh data that may still change and matches the Search Console UI; 'final' is finalized data only (lags 2-3 days).	all
`dimensions`	No	Group rows by these. Omit for ['page'] (['date'] with byNewsShowcasePanel); [] for totals.
`start_date`	No	First day, YYYY-MM-DD in Pacific Time. Defaults to 28 days ago.
`aggregation_type`	No	'auto' aggregates by page. byNewsShowcasePanel counts News Showcase panels instead: it needs the filter searchAppearance equals NEWS_SHOWCASE and cannot group or filter by page, so dimensions default to ['date'] with it.	auto

Output Schema

TableJSON Schema

Name	Required	Description
`rows`	Yes	One object per row: dimension values by name, then clicks, impressions, ctr (0-1) and position (absent for Discover and Google News).
`notes`	No
`request`	Yes	The exact request body sent to Google.
`end_date`	Yes
`site_url`	Yes
`row_count`	Yes
`data_state`	Yes
`dimensions`	Yes
`start_date`	Yes
`search_type`	Yes
`next_start_row`	No	Pass as start_row to fetch the next page, if there is one.
`aggregation_type`	No
`first_incomplete_date`	No
`first_incomplete_hour`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Oct 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: data availability is limited to sites appearing in Discover feeds, and certain metrics simply do not exist. Pagination and data-state behavior are left to the schema rather than the description.

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 with zero waste. The positive statement of what the tool returns is front-loaded, and the limiting caveats follow. Nothing is repeated from the schema or annotations.

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 an output schema present and 100% parameter coverage, the description only needs to carry the Discover-specific gotchas, which it does (no query/position/device data, feed-only coverage). What remains uncovered — aggregation_type behavior and paging — is fully described in the schema, so nothing critical is missing.

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%, so every parameter is already documented in detail by the schema. The description only restates the available grouping dimensions, adding no syntax, default or constraint information beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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 first sentence names the exact resource (Google Discover performance) and enumerates the metrics and grouping dimensions (clicks, impressions, CTR by page, country or date). An agent can distinguish it from query_search_analytics by the resource name alone. It stops short of explicitly contrasting itself with the other query_*_analytics siblings.

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

Usage Guidelines4/5

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

The second sentence gives strong negative guidance: Discover has no query, average-position or device data, and only covers sites that appear in Discover feeds — which steers the agent away from this tool when those dimensions are needed. It never names an alternative sibling (e.g. query_search_analytics) to use instead, so routing requires inference.

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