gsc-mcp

Batch Search Analytics

batch_search_analytics

Execute multiple Google Search Console search analytics queries in a single call to retrieve performance data for multiple sites or date ranges without individual requests.

Instructions

Run multiple search analytics queries in one call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`queries`	Yes	List of query dicts. Each dict supports: site_url (required), start_date, end_date, dimensions, search_type, data_state, row_limit, filters.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 21, 2026

TDQS

A3.7/5.0

Behavior2/5

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

Annotations are absent, so the description carries the full burden. It does not disclose whether the operation is read-only, any rate limits, how results are aggregated, or any side effects. For a batch tool with no annotation coverage, this is a significant gap.

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?

A single, concise sentence that front-loads the core action without any waste. Every word earns its place.

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

Completeness3/5

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

While an output schema exists (so return values are covered), the description omits details about batch behavior, such as limits on the number of queries, parallel execution, or how results are combined. Given the batch complexity, more context would be beneficial.

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?

The schema covers 100% of parameters with a detailed description of the 'queries' array and its fields. The description adds no extra semantics beyond the schema, so it meets the baseline for full schema coverage.

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 description clearly states a specific verb ('run') with a specific resource ('search analytics queries') and scope ('multiple in one call'). It effectively distinguishes this batch tool from the single-query sibling get_search_analytics, so an agent can tell them apart.

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 implies usage for batching multiple queries, which provides clear context. However, it does not explicitly name the alternative for single queries (get_search_analytics) or state when not to use this tool, leaving some inference to the agent.

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