SEO GSC Wizard MCP

Submit a sitemap to Search Console

submit_sitemap

Idempotent

Submits (or re-submits) an existing sitemap URL to Google Search Console for a property, the same action as "Add a new sitemap" in the Sitemaps report. It does not create or host a sitemap: the file must already be published and reachable at the URL you pass; this only registers it with Google or asks Google to fetch it again after new content went live. Every sitemap URL must be on the property host or a subdomain of it. Up to 20 sitemaps per call. Submitting is idempotent and queues a download; it does not index anything by itself, and Google reports parse warnings/errors only after it has fetched the file, so a freshly submitted sitemap normally comes back pending. Requires a Google account connected with full Search Console access (a read-only connection is refused before anything is sent). If a rate limit or a permission refusal stops a batch after some sitemaps were accepted, the accepted ones are still reported and the rest are listed in notAttempted, with stopReason. Use list_sitemaps to see what is already submitted.

Input Schema

Name	Required	Description	Default
`siteUrl`	Yes
`sitemapUrls`	Yes	Absolute URLs of already-published sitemaps, e.g. ["https://example.com/sitemap_index.xml"]. Each must be on the property host or a subdomain of it. Max 20.

Output Schema

Name	Required	Description	Default
`failed`	No
`actions`	No
`message`	No
`results`	No
`siteUrl`	No
`attempted`	No
`submitted`	No
`stopReason`	No
`notAttempted`	No
`retryAfterSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedOutput schema / properties / results / items / additionalProperties
```
Previous value: -falseNew value: +true
```

Changed5 schema fields changedOct 10, 2026

addedOutput schema / properties / actions / $ref
```
Added value: +"#/properties/notAttempted"
```

removedOutput schema / properties / actions / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / notAttempted

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / retryAfterSeconds

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

addedOutput schema / properties / stopReason

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

First observedOct 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: queueing a download rather than indexing, parse warnings only appearing after fetch, the property-host/subdomain constraint, 20-per-call cap, full-access auth requirement with read-only refused, and partial-batch failure reporting via notAttempted/stopReason. This is exactly the operational context annotations cannot express.

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?

Front-loaded with the core action, mapping to the UI, and constraints in a logical order. It is somewhat dense and repeats the 'does not create/host' point twice in one sentence, but no sentence is genuinely wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, yet the description still covers the failure shape (accepted vs notAttempted with stopReason), auth requirements, rate limits, and idempotency. Nothing an agent needs to call this correctly is missing.

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?

With only 50% schema description coverage, the description should compensate for the undocumented siteUrl. It only implies siteUrl is the property ('for a property', 'the property host') without giving expected format, and its per-URL host/subdomain and max-20 notes largely restate the sitemapUrls schema description rather than adding new meaning.

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 (submits/re-submits) on a specific resource (an existing sitemap URL) for a property, and maps it to the exact UI action ('Add a new sitemap'). It clearly separates itself from neighbors like list_sitemaps and get_sitemap_performance, which an agent can distinguish without opening any 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?

Gives explicit preconditions and exclusions: the file must already be published and reachable, this only registers it with Google or asks for a re-fetch after new content, and it does not create or host anything. It also routes the agent to a sibling ('Use list_sitemaps to see what is already submitted') for the read case.

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?