Google Search Console MCP Server

Overview Schema Source Related Servers Discussions Admin

Query Google News performance

query_google_news_analytics

Read-only

Get Google News clicks, impressions, and CTR by page, country, device, or date for a Search Console property. Use it for news.google.com and app performance; no queries or average position.

Instructions

Google News performance (news.google.com and the Google News app): clicks, impressions and CTR by page, country, device or date. Google News reports no queries and no average position. For the News tab in Google Search, use query_news_tab_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 ['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/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 a genuinely useful behavioral constraint not in annotations or schema: Google News carries no query or average-position data, which shapes what the agent can ask for. It does not discuss paging or data freshness, but the schema covers those.

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?

Three tight sentences, front-loaded with scope and metrics before the disambiguation and the negative constraint. Every sentence carries distinct information; nothing is redundant.

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?

An output schema exists, so return values need no explanation. For a 9-parameter, 100%-covered read tool, the description supplies the scope, the metric limitations, and the sibling routing rule — everything an agent needs to select and invoke it correctly.

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 one of the 9 parameters (including the nuanced aggregation_type and data_state) is already documented in the schema. The description adds no parameter-level detail beyond the metric/dimension list, so the baseline 3 applies.

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?

States a specific verb+resource (Google News performance) and enumerates the metrics returned (clicks, impressions, CTR) plus the dimensions available (page, country, device, date). It explicitly names the sibling it is not, query_news_tab_analytics, so an agent can disambiguate the two news tools without opening either schema.

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

Usage Guidelines5/5

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

Provides an explicit routing rule: 'For the News tab in Google Search, use query_news_tab_analytics,' with the condition that selects the alternative. It also pre-empts wrong usage by stating Google News reports no queries and no average position, so the agent knows not to expect those metrics.

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