grr

Overview Schema Source Related Servers Discussions Admin

searchconsole.sitemaps.list

List sitemaps submitted for a site or included in a sitemap index to inspect Search Console coverage. Provide siteUrl, and optionally sitemapIndex, to retrieve entries as JSON.

Instructions

Lists the sitemaps-entries submitted for this site, or included in the sitemap index file (if sitemapIndex is specified in the request) [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: delete, get, submit.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`siteUrl`	Yes	[URL path segment] The site's URL, including protocol. For example: `http://www.example.com/`.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`sitemapIndex`	No	[query parameter] A URL of a site's sitemap index. For example: `http://www.example.com/sitemapindex.xml`.

Output Schema

Name	Required	Description	Default
`sitemap`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / siteUrl / description

Previous value: -"The site's URL, including protocol. For example: `http://www.example.com/`."New value: +"[URL path segment] The site's URL, including protocol. For example: `http://www.example.com/`."

changedInput schema / properties / sitemapIndex / description

Previous value: -"A URL of a site's sitemap index. For example: `http://www.example.com/sitemapindex.xml`."New value: +"[query parameter] A URL of a site's sitemap index. For example: `http://www.example.com/sitemapindex.xml`."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "sitemap": {
+      "items": {
+        "properties": {
+          "contents": {
+            "items": {
+              "properties": {
+                "indexed": {
+                  "type": "string"
+                },
+                "submitted": {
+                  "type": "string"
+                },
+                "type": {
+                  "enum": [
+                    "WEB",
+                    "IMAGE",
+                    "VIDEO",
+                    "NEWS",
+                    "MOBILE",
+                    "ANDROID_APP",
+                    "PATTERN",
+                    "IOS_APP",
+                    "DATA_FEED_ELEMENT"
+                  ],
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "errors": {
+            "type": "string"
+          },
+          "isPending": {
+            "type": "boolean"
+          },
+          "isSitemapsIndex": {
+            "type": "boolean"
+          },
+          "lastDownloaded": {
+            "type": "string"
+          },
+          "lastSubmitted": {
+            "type": "string"
+          },
+          "path": {
+            "type": "string"
+          },
+          "type": {
+            "enum": [
+              "NOT_SITEMAP",
+              "URL_LIST",
+              "SITEMAP",
+              "RSS_FEED",
+              "ATOM_FEED",
+              "PATTERN_SITEMAP",
+              "OCEANFRONT"
+            ],
+            "type": "string"
+          },
+          "warnings": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, but the description discloses the HTTP method (GET), the response format (JSON), and request construction rules involving typed parameters, `params`, and `body_file`. It does not mention authentication or pagination, but for a read-only list endpoint the core behavior is sufficiently transparent.

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?

The description is front-loaded with the key operation and remains reasonably compact. The second sentence is somewhat run-on and includes generic body-construction details that are less relevant for a GET list endpoint, but it does not waste many words.

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?

Given the full schema coverage and the presence of an output schema, the description provides enough context for correct invocation: resource scope, conditional `sitemapIndex` behavior, HTTP method, and sibling tool awareness. Additional auth or pagination notes would help, but are not strictly necessary here.

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 100%, so the baseline is 3. The description adds useful behavioral meaning for `sitemapIndex` and explains precedence between typed parameters and the `params` map, plus the role of `body_file`, which goes beyond the schema's field-level documentation.

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 states a specific verb (Lists) and resource (sitemaps-entries submitted for this site), and explicitly distinguishes the tool from its siblings on the same resource: delete, get, and submit. An agent can identify the operation without opening the schema.

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 gives clear context for when this tool is appropriate, including the conditional behavior when `sitemapIndex` is specified. It also names sibling tools over the same resource, though it does not spell out explicit when-not conditions or detailed alternatives.

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

Deploy Server