Sam GSC MCP

list_sitemaps_enhanced

Read-onlyIdempotent

Retrieve detailed sitemaps for a Google Search Console property, including pending counts and optional child sitemaps under a sitemap index, to diagnose indexing coverage and SEO issues.

Instructions

Detailed sitemap list, optionally the children of one sitemap index, with pending counts.

Args: site_url: Exact property (defaults to GSC_SITE_URL) sitemap_index: Optional sitemap index URL to list its child sitemaps

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sitemaps_enhanced"
  }
}

Input Schema

Name	Required	Description	Default
`site_url`	No
`sitemap_index`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 24, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only 'with pending counts' as extra behavioral detail, and nothing about the GSC_SITE_URL fallback behavior at runtime or any rate-limit/quota considerations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded summary sentence followed by a short args block; no filler. The 'Args:' formatting is slightly redundant with the schema, but the parameter notes themselves carry information the schema lacks.

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?

An output schema exists, so return values need not be explained, and both parameters are meaningfully described. The remaining gap is sibling disambiguation against get_sitemaps and get_sitemap_details, which matters given several overlapping sitemap tools in the toolset.

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 carries the burden and mostly does: site_url is described as an 'Exact property' with a GSC_SITE_URL default, and sitemap_index as an optional index URL whose children are returned. Missing only format examples (e.g., 'sc-domain:' vs 'https://' property forms).

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 and resource ('Detailed sitemap list') plus a scope variant ('children of one sitemap index') and an output characteristic ('pending counts'). It does not, however, distinguish itself from the sibling tools get_sitemaps and get_sitemap_details, which an agent could easily confuse with this 'enhanced' listing.

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

Usage Guidelines2/5

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

The word 'optionally' hints at the two modes, but there is no explicit when-to-use guidance, no statement of when to prefer this over get_sitemaps or get_sitemap_details, and no prerequisites (e.g., auth or site access). The agent must infer routing from the name alone.

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