google-search-console-mcp

Overview Schema Source Related Servers Discussions Admin

Submit several sitemaps

submit_sitemaps

Idempotent

Submit up to 50 sitemaps for a Search Console property in one call, with individual success or failure for each. Avoids a round trip per sitemap, making large-site submission practical.

Instructions

Submits up to 50 sitemaps for one property in a single call, reporting success or failure per entry. The API has no batch method — this makes the calls one after another — but it saves a round trip per sitemap, which is what makes a large site practical. One failure does not stop the rest.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`site_url`	Yes	The Search Console property: "sc-domain:example.com" for a domain property, or "https://example.com/" for a URL-prefix property (the trailing slash is required)
`feedpaths`	Yes	The full URLs of the sitemaps to submit

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes
`truncated`	No	Present only when entries were dropped to fit the budget.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.0Sep 8, 2026
- addedInput schema / properties / feedpaths / items / maxLength
```
Added value: +2048
```
- addedInput schema / properties / site_url / maxLength
```
Added value: +2048
```
First observedv0.2.0Sep 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations (idempotent, non-destructive), the description adds useful behavioral details: per-entry success/failure reporting and partial failure isolation. This helps the agent understand what to expect in mixed-result scenarios.

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?

The description is concise and well-structured, conveying all essential information without unnecessary padding. It efficiently covers purpose, batch behavior, and failure handling in a few sentences.

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?

Given that an output schema is present, the description need not detail return values. It adequately covers the core operation, including limits and partial failure, making it self-contained for the agent.

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% for both parameters, providing clear meaning. The tool description itself does not add further parameter-specific clarification, so a baseline of 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 clearly states the action (submit sitemaps), the resource (sitemaps), the scope (up to 50 for one property), and the batch nature. It distinguishes itself from the sibling submit_sitemap by emphasizing 'single call' and per-entry reporting.

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?

It explains the trade-off between this batch tool and making individual calls, noting that it saves round trips while not being a true server-side batch. This gives context for when to use it, though it doesn't explicitly say 'use this when you have multiple sitemaps'.

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