Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

search_console_list_sitemaps

Retrieve submitted sitemaps for a Google Search Console property to verify indexing coverage. Filter by sitemap index URL to inspect child sitemaps.

Instructions

List submitted sitemaps for a Search Console property.

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": "search_console_list_sitemaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlNoSearch Console property, for example sc-domain:example.com. Use list_sites to find one.
sitemap_indexNoOptional sitemap index URL used to filter child sitemaps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'List' implies a read-only operation, but the definition says nothing about authentication requirements, pagination, result size, or whether warnings/errors on submitted sitemaps are included.

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?

A single front-loaded sentence with no redundant wording. It is efficient but borders on under-specification, leaving no room for the scoping or filtering nuance an agent might want.

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?

This is a simple two-parameter read tool with no output schema and fully documented parameters, so the bar is modest. Still, the definition does not say what a returned list contains (sitemap URLs only vs. status/warnings) or whether the optional filter narrows results, leaving a small but real gap.

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%, so both site_url and sitemap_index are already documented, including the example format and the pointer to list_sites. The description adds no further meaning about how sitemap_index filtering behaves, which is acceptable at the baseline for full schema coverage.

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 states a specific verb and resource ('List submitted sitemaps') scoped to a Search Console property, which is clear enough for an agent to understand. It does not distinguish itself from any sibling tool (e.g., why not list_sites or inspect_url for sitemap-related checks), so it stays short of a 5.

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?

Usage is implied by the tool name and the 'submitted sitemaps' phrase, and the site_url schema description usefully points to list_sites for discovery. However, the definition itself gives no when-to-use or when-not-to-use guidance, no mention of alternatives for inspecting sitemap contents, and no prerequisites.

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