GSC MCP Server

delete_sitemap

Remove a submitted sitemap from Google Search Console to halt its processing and prevent indexing.

Instructions

Delete (unsubmit) a sitemap from Google Search Console.

Args: site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or "sc-domain:example.com"). Domain properties cover all subdomains — use the domain property as site_url and filter by page to analyze a specific subdomain. sitemap_url: The full URL of the sitemap to delete

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": {
      "site_url": "<site_url>",
      "sitemap_url": "<sitemap_url>"
    },
    "name": "delete_sitemap"
  }
}

Input Schema

Name	Required	Description	Default
`site_url`	Yes
`sitemap_url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Aug 7, 2026

TDQS

A4.1/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits on its own. It only states the obvious 'delete' action without elaborating on side effects, reversibility, or required permissions. The term 'unsubmit' adds slight clarity but not enough to cover the absence of annotations.

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: a single-sentence purpose followed by a clean Args section. Every sentence adds value, with no redundancy or fluff.

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 two-parameter delete tool, the description covers the essential purpose and parameter semantics. It does not mention that the sitemap must already be submitted or that deletion only affects GSC, but these are likely implied by the tool's nature. The presence of an output schema means return values don't need explanation. Overall, adequately complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description fully compensates by explaining both parameters in detail. It gives a concrete example for site_url, explains domain vs URL-prefix properties, and clarifies that sitemap_url should be the full URL. This adds significant value beyond the schema's bare field names.

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: 'Delete (unsubmit) a sitemap from Google Search Console.' The verb 'Delete' with the resource 'sitemap' is specific and distinguishes it from sibling tools like 'submit_sitemap' and 'get_sitemaps'.

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 provides practical guidance on the site_url parameter, explaining the difference between URL-prefix and domain properties with an example. This is useful context for correct usage, though it doesn't explicitly state when to use this tool over alternatives or mention prerequisites.

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