Google Search Console MCP Server

batch_url_inspection

Batch-inspect multiple URLs in Google Search Console to retrieve indexation status and live data for each page, saving time over individual inspections.

Instructions

Inspect multiple URLs in batch (within API limits).

Args:
    site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
              "sc-domain:example.com"). Domain properties cover all subdomains — use the
              domain property as site_url and filter by page to analyze a specific subdomain.
    urls: List of URLs to inspect, one per line

Input Schema

TableJSON Schema

Name	Required	Description	Default
`urls`	Yes
`site_url`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Aug 2, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. 'Within API limits' is vague and gives no concrete limit, error behavior, or side-effect information. The read-only nature is only implied, not stated.

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 compact and front-loaded with the core purpose. The Args section adds essential parameter guidance without fluff, and every line contributes meaning.

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?

Input semantics are well-covered and an output schema exists, so return values do not need explanation. However, the description lacks concrete batch-limit numbers and does not guide the agent toward or away from the single-URL sibling tool. These gaps matter for a tool with no annotations.

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?

With 0% schema coverage, the description fully compensates. It explains that site_url must be an exact GSC property URL from list_properties, gives example formats, and clarifies domain-property subdomain coverage. It also specifies that urls must be provided one per line.

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 clearly states the verb and resource: 'Inspect multiple URLs in batch'. The batch qualifier distinguishes this from sibling tools like inspect_url_enhanced, though it does not explicitly name the alternative.

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?

The batch scope implies it is intended for inspecting multiple URLs at once, and the site_url guidance references list_properties as a prerequisite. However, there is no explicit statement about when to choose this over inspect_url_enhanced or any batch-limit threshold.

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

Deploy Server