Skip to main content
Glama
shutovdef-dotcom

Google Search Console MCP Server

batch_url_inspection

Submit a list of URLs to inspect their Google Search Console status, including index coverage and performance data, in one batch operation.

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
NameRequiredDescriptionDefault
urlsYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions batch and API limits but gives no details on rate limits, error handling, partial success, or failure behavior. For a batch operation, more behavioral context is needed.

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 concise with a clear Args section. No extraneous words; every sentence provides value. It is well-structured and easy to parse.

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?

Given the batch complexity and existence of an output schema, the description covers main points but misses rate limits, error handling, and input format specifics. It is adequate but could be more complete.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate. It explains site_url with examples and domain property coverage, and urls as a list per line. This adds meaning beyond the schema, but lacks constraints like max URL count or format validation.

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 the tool inspects multiple URLs in batch within API limits. The verb 'inspect' and resource 'multiple URLs' are specific, and the batch aspect distinguishes it from single-URL siblings like inspect_url_enhanced.

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 description mentions 'within API limits' and explains domain property usage, but does not explicitly state when to use this tool versus alternatives (e.g., for bulk vs. single inspection). No exclusion criteria or when-not-to-use guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shutovdef-dotcom/google-search-console-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server