Skip to main content
Glama

list_sitemaps

Retrieve all sitemaps submitted for a site in Google Search Console to review which sitemap files are registered.

Instructions

List all sitemaps submitted for a site in Google Search Console.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteUrl": "<siteUrl>"
    },
    "name": "list_sitemaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlYesSite URL as it appears in Search Console

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0-fork.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. 'List all' signals a read-only, unfiltered operation, but nothing is said about whether results include sitemap index children, per-sitemap status/error fields, pagination limits, or whether the call requires verified ownership of the site.

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 filler. It is appropriately sized for a one-parameter listing tool, though a brief clause about output or scope would not have hurt.

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?

For a simple one-parameter read tool with no output schema, the definition covers what the tool does and which site it acts on. It omits what the returned entries contain and any ownership or permission context, which an agent would need to interpret results.

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% and the single siteUrl parameter is already documented as the URL as it appears in Search Console. The description adds no format examples, no mention of the domain-vs-URL-prefix property conventions, and no meaning beyond what the schema provides; 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?

The description states a specific verb and resource ('List all sitemaps') and scopes it to a site in Google Search Console, which is enough to distinguish it from list_sites, inspect_url, and search_analytics on resource alone. It stops short of naming or contrasting with any sibling explicitly.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as inspecting an individual sitemap or listing sites. The only implied usage comes from restating the purpose.

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

Deploy Server

Other Tools