Google Search Console MCP Server

Overview Schema Source Related Servers Discussions Admin

Query News tab performance

query_news_tab_analytics

Read-only

Retrieve performance in the News tab of Google Search: clicks, impressions, CTR, and average position, by query, page, country, device, or date.

Instructions

Performance in the News tab of Google Search: clicks, impressions, CTR and average position, by query, page, country, device or date. For news.google.com and the Google News app, use query_google_news_analytics.

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 ['query']; [] for totals. searchAppearance must be the only dimension.
`start_date`	No	First day, YYYY-MM-DD in Pacific Time. Defaults to 28 days ago.
`aggregation_type`	No	'auto' is right almost always. byProperty cannot be used with page grouping or filters.	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.1/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 no behavioral context beyond that — e.g., data freshness/lag handling, pagination behavior, or the effects of combining multiple filters — even though the 'final' vs 'all' distinction and daily row limits are real operational traits. With annotations carrying the safety burden, a 3 is appropriate.

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, each earning its place: the first defines the data and metrics, the second does the sibling routing. The most important content (what the tool returns) is front-loaded, and there is no filler.

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

Completeness5/5

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

With a full output schema, 100% schema description coverage, and annotations covering the safety profile, the description only needs to establish scope and sibling routing, which it does cleanly. Nothing an agent needs to select or invoke the tool correctly 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 (filters, dates, dimensions, aggregation_type, data_state, paging) is already documented with enums and defaults in the schema. The description contributes no additional parameter meaning beyond naming dimension categories. Baseline 3 is correct when the schema does all the heavy lifting.

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

Purpose5/5

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

The first sentence names the specific data surface (News tab of Google Search) and enumerates the returned metrics plus available breakdown dimensions, so the agent knows exactly what the tool produces. It also explicitly distinguishes itself from query_google_news_analytics, which covers news.google.com and the Google News app. This is a specific verb+resource+scope that no sibling duplicates.

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 description routes the agent away from this tool for news.google.com/Google News app use cases, naming the correct alternative. It does not, however, explain the boundary against query_search_analytics or when News-tab data is the right choice versus general Search performance, so the guidance is clear but not exhaustive.

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