Google Search Console MCP Server

Overview Schema Source Related Servers Discussions Admin

Query one search appearance

query_search_appearance

Read-only

Retrieve performance metrics for a specific search appearance, broken down by query, page, country, device, or date. Use the exact appearance name from list_search_appearances.

Instructions

Step two: performance of one search appearance, broken down by query, page, country, device or date. Get the appearance name from list_search_appearances.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filters`	No	Extra filters, combined with AND with the appearance.
`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.
`appearance`	Yes	Exact appearance name from list_search_appearances, such as VIDEO or REVIEW_SNIPPET.
`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	Break the appearance down by these. Omit for ['query'] (['page'] for Discover and Google News).
`start_date`	No	First day, YYYY-MM-DD in Pacific Time. Defaults to 28 days ago.
`search_type`	No		web

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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the workflow sequencing context but says nothing about freshness, pagination behavior, or quota concerns beyond what the schema's data_state field already documents. Adequate, not rich.

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 tight sentences with zero waste. The purpose and the prerequisite are both front-loaded and every clause earns its place.

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 and annotations already present, the description needn't explain return values. It supplies the one thing the schema cannot: the sequencing dependency on list_search_appearances. Slightly light on how it relates to the sibling analytics tools, but essentially complete.

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 90%, so the schema already documents nearly every parameter (filters, dates, pagination, data_state, dimensions). The description echoes the breakdown dimensions but adds no format or syntax detail beyond the schema, so baseline 3 is appropriate.

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+resource ('performance of one search appearance') and the breakdown dimensions, which clearly differentiates it from keyword-level siblings like query_search_analytics. It stops short of explicitly naming the sibling it differs from, so an agent must infer the distinction.

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?

Positions the tool as 'step two' in a workflow and gives the prerequisite: 'Get the appearance name from list_search_appearances.' That routes the agent to the correct source for the required 'appearance' argument. No explicit when-not guidance or mention of the sibling analytics tools, so it falls short of a 5.

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