Skip to main content
Glama
Akxan

google-seo-mcp

by Akxan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List sitemaps

gsc_list_sitemaps
Read-onlyIdempotent

List sitemaps submitted for a Search Console property to see status, errors, warnings, and URL counts. Pass a sitemap index URL to inspect child sitemaps and find the source of issues.

Instructions

List sitemaps submitted for a property, with last submitted/downloaded times, errors, warnings and URL counts. Pass sitemapIndex to list the child sitemaps inside an index file with their own counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteUrlYesSearch Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites).
sitemapIndexNoSitemap index URL, e.g. 'https://example.com/sitemap_index.xml': lists its child sitemaps instead of the submitted ones, which is how you find which child file holds the errors or warnings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • changedInput schema / properties / siteUrl / description
      Previous value: -"Search Console property, e.g. 'sc-domain:example.com' or 'https://example.com/' (see gsc_list_sites)."New value: +"Search Console property, e.g. 'sc-domain:example.com' (see gsc_list_sites)."
    • addedInput schema / properties / sitemapIndex
      Added value: +{
+  "description": "Sitemap index URL, e.g. 'https://example.com/sitemap_index.xml': lists its child sitemaps instead of the submitted ones, which is how you find which child file holds the errors or warnings.",
+  "format": "uri",
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / siteUrl / description
      Previous value: -"Property URL exactly as shown in Search Console, e.g. 'https://example.com/' or 'sc-domain:example.com'. Use gsc_list_sites to discover it."New value: +"Search Console property, e.g. 'sc-domain:example.com' or 'https://example.com/' (see gsc_list_sites)."
  3. First observedv0.3.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it returns last submitted/downloaded times, errors, warnings, and URL counts, and explains the sitemapIndex behavior. However, it doesn't disclose details like pagination, response size, or what happens when no sitemaps exist, which would be useful for a listing tool.

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 with zero waste. The main purpose is front-loaded, and the sitemapIndex behavior is explained in a single follow-up sentence. Every word earns its place.

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?

For a read-only listing tool with 100% schema coverage and no output schema, the description is nearly complete. It explains the main use case, the sitemapIndex variant, and what data is returned. The only minor gap is that it doesn't mention what happens when no sitemaps are submitted or whether the response includes a list of sitemap types (e.g., sitemap vs index), but these are minor against the annotations and schema.

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 the schema already documents both parameters well. The description adds a bit of value by explaining the purpose of sitemapIndex ('lists its child sitemaps instead of the submitted ones') and the use case for finding errors/warnings, but it doesn't add syntax or format details beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb ('List') and resource ('sitemaps submitted for a property'), and immediately distinguishes itself from sibling tools like gsc_submit_sitemap and gsc_delete_sitemap by focusing on listing. It also adds the sitemapIndex behavior, which differentiates it from a generic sitemap list.

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

Usage Guidelines4/5

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

The description clearly states when to use the tool (list submitted sitemaps) and when to use the sitemapIndex parameter (to list child sitemaps inside an index file). It doesn't explicitly name alternatives or exclusions, but the context is clear enough for an agent to select it over siblings like gsc_submit_sitemap or sitemap_check.

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