GSC SEO MCP

Overview Schema Source Related Servers Discussions Admin

submit_sitemap

Submit or refresh a sitemap in Google Search Console to notify Google of new or updated content, helping ensure proper indexing.

Instructions

Submit or refresh a sitemap in Search Console. Requires write scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feedpath": "<feedpath>"
    },
    "name": "submit_sitemap"
  }
}

Input Schema

Name	Required	Description	Default
`siteUrl`	No	Google Search Console property URL, e.g. sc-domain:example.com or https://www.example.com/.
`feedpath`	Yes	Full sitemap URL.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations exist, so the description must carry the full behavioral disclosure. It mentions 'write scope' as a requirement, but does not explain what 'refresh' means, rate limits, or consequences of submission (e.g., if sitemap already exists).

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 no wasted words. The first sentence front-loads the purpose, and the second adds a key requirement. Highly concise.

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 simple tool with two fully described parameters and no output schema, the description provides enough context to understand the core function and a critical prerequisite. However, it could elaborate on the 'refresh' aspect and what the agent should expect.

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 baseline is 3. The description adds no additional parameter information beyond what the schema already provides, such as constraints or formats.

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 verb 'Submit or refresh' and resource 'a sitemap in Search Console', providing a specific action and context. It distinguishes from sibling tools like delete_sitemap and list_sitemaps.

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

Usage Guidelines3/5

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

Implies usage through 'Requires write scope', but does not explicitly mention when to use this tool versus alternatives. No exclusions or when-not guidance provided.

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