Sam GSC MCP

get_advanced_search_analytics

Read-onlyIdempotent

Query Google Search Console search analytics with pagination, sorting, regex filters, and multi-filter AND logic to extract targeted SEO performance data up to 25,000 rows per call.

Instructions

Power query: up to 25,000 rows per call with pagination, sorting, regex and multi-filter AND logic.

Args: site_url: Exact property from list_properties (defaults to GSC_SITE_URL) start_date: YYYY-MM-DD (defaults to days ago) end_date: YYYY-MM-DD (defaults to latest day) dimensions: comma list or array, e.g. "query,page,device" search_type: web, image, video, news, discover, googleNews row_limit: Max rows (1-25000, default 1000) start_row: Offset for pagination (use next_start_row from the previous page) sort_by: clicks, impressions, ctr or position (applied to returned rows) sort_direction: descending or ascending (ascending position = best rankings first) filter_dimension: Single filter dimension (query, page, country, device, searchAppearance) filter_operator: equals, notEquals, contains, notContains, includingRegex, excludingRegex filter_expression: Value for the single filter filters: JSON array of filters (AND). Overrides the single-filter args. data_state: "all" (default) or "final" days: Look-back window when start_date is omitted (default 28)

Input Schema

Name	Required	Default
`days`	No
`filters`	No
`sort_by`	No	clicks
`end_date`	No
`site_url`	No
`row_limit`	No
`start_row`	No
`data_state`	No
`dimensions`	No	query
`start_date`	No
`search_type`	No	web
`sort_direction`	No	descending
`filter_operator`	No	contains
`filter_dimension`	No
`filter_expression`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is read-only, idempotent, non-destructive and open-world. The description adds meaningful behavior: a 25,000-row cap, pagination mechanics, sorting applied to returned rows, regex filter support, AND logic for multi-filters, and data_state options.

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?

The description is front-loaded with the key capability, then uses a clean argument list for a 15-parameter tool. Every line adds operational meaning and there is no redundant prose.

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?

For a complex 15-parameter analytics query tool, the description covers the important calling constraints, defaults, pagination, filtering, sorting, and data freshness options. Since an output schema exists, it does not need to explain return values.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full parameter burden and does so thoroughly. It documents defaults, date formats, allowed search types, row limits, pagination usage, sort fields and direction semantics, filter dimensions/operators, and the filters override rule.

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 makes clear this is a high-volume search analytics query tool with pagination, sorting, regex and multi-filter AND logic. It does not explicitly name Google Search Console or distinguish itself from the sibling get_search_analytics, but the resource and capabilities are still identifiable.

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

Usage Guidelines3/5

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

It gives operational guidance such as using next_start_row from the previous page and that filters overrides the single-filter args. However, it does not say when to use this tool versus get_search_analytics, export_search_analytics, compare_search_periods, or other analytics siblings.

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