SEO GSC Wizard MCP

List submitted sitemaps

list_sitemaps

Read-only

Use this when the user asks which sitemaps a property has and whether Google read them. Lists every sitemap submitted to Search Console for a property, sorted by path, with submission timestamps, warning/error counts, and the submitted URL count per content type (indexed is null: Google deprecated it). Not for a sitemap's traffic or indexing: use get_sitemap_performance.

Input Schema

Name	Required	Description	Default
`siteUrl`	Yes

Output Schema

Name	Required	Description
`note`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`siteUrl`	No
`nextStep`	No
`ordering`	No
`sitemaps`	No
`sortedBy`	No
`sortOrder`	No
`thenOrder`	No
`emptyBecause`	No
`methodLimits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Name of the top-level field that holds the rows sortedBy describes."
+}

addedOutput schema / properties / note

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

removedOutput schema / properties / sitemaps / items / properties / contents / $ref
```
Removed value: -"#/properties/sitemaps/items/properties/warnings"
```

addedOutput schema / properties / sitemaps / items / properties / contents / anyOf

Added value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "indexed": {
+          "type": "null"
+        },
+        "submitted": {
+          "$ref": "#/properties/sitemaps/items/properties/warnings"
+        },
+        "type": {
+          "$ref": "#/properties/siteUrl"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

Changed10 schema fields changedOct 18, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / emptyBecause

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / methodLimits

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / nextStep

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / ordering

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "sortOrder": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "sortedBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenOrder": {
+            "$ref": "#/properties/siteUrl"
+          }
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / sitemaps / items / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / sortOrder

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / sortedBy

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / thenBy

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / thenOrder

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

First observedOct 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds real value on top: sort order (by path), returned fields (submission timestamps, warning/error counts, submitted URL count by content type), and the notable quirk that indexed is null because Google deprecated it. That deprecation note prevents an agent from misinterpreting a null field. It stops short of anything about permissions or call cost, hence a 4.

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, front-loaded with the trigger condition, then the return shape, then the sibling hand-off. The parenthetical about indexed being deprecated is the only aside and it earns its place by preventing a null-misread.

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?

An output schema exists, so the description is not obligated to enumerate return values, yet it usefully previews the key ones. For a single-parameter read tool with full annotation coverage the description is nearly complete; the only real gap is the siteUrl format convention, which neither schema nor description supplies.

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?

There is one parameter at 0% schema description coverage, so the description carries the burden and only implies it via 'for a property.' It does not state the expected siteUrl format (full URL vs. sc-domain: prefix) or that it must be a property the account can access, which is exactly the ambiguity an agent will hit at call time.

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?

States a specific verb and resource (lists every sitemap submitted to Search Console for a property) plus the scope and ordering. It explicitly separates itself from get_sitemap_performance, which handles traffic/indexing, so an agent can distinguish it from siblings 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 Guidelines5/5

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

Opens with the exact user question that should trigger it ('which sitemaps a property has and whether Google read them') and closes with an explicit exclusion plus the named alternative: traffic or indexing questions go to get_sitemap_performance. Both the when and the when-not are stated.

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

All SEO GSC Wizard MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?