Google Search Console MCP Server

Overview Schema Source Related Servers Discussions Admin

Inspect many URLs

batch_inspect_urls

Read-only

Inspect up to 50 URLs concurrently, summarize index verdicts, and report per-URL failures or quota-skipped URLs so you can retry them later.

Instructions

Inspect up to 50 URLs concurrently and summarize their index verdicts. Failures are reported per URL; if the daily quota runs out, the remaining URLs are skipped and listed so you can retry them later.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`urls`	Yes	1-50 page URLs.
`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.
`language_code`	No	BCP-47 language for issue messages, e.g. 'en-US' or 'de-DE'.	en-US

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`notes`	No
`site_url`	Yes
`verdict_counts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Oct 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the readOnlyHint=true and openWorldHint=false annotations, the description discloses genuinely useful behavior: per-URL failure reporting, partial completion when the daily quota runs out, and that skipped URLs are listed for later retry. It stops short of saying whether verdicts are cached or how long a quota reset takes.

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, zero filler, and the capability and its limit are front-loaded ahead of the edge-case behavior. Every clause carries information an agent would otherwise have to guess.

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

Completeness4/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-shape explanation is rightly omitted, and the description covers the quota and partial-failure cases an agent must handle. It is slightly incomplete in not clarifying that all URLs must belong to the single required site_url property, which affects how the batch should be constructed.

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%: maxItems=50, the site_url property-resolution rules, and the BCP-47 language_code default are all documented in the schema. The description's 'up to 50 URLs' only restates maxItems, adding no syntax or format detail beyond the structured fields, so the baseline 3 applies.

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?

States a specific verb (inspect) and resource (URLs) plus scope: batch, up to 50, concurrent, summarizing index verdicts. It never names the sibling inspect_url, so an agent must infer the batch-vs-single distinction from the name and the '50 URLs' limit.

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 50-URL concurrency and quota-exhaustion notes imply bulk use, but there is no explicit statement of when to prefer this over inspect_url, nor any exclusion such as single-URL checks or URLs belonging to different properties.

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