Skip to main content
Glama
Sign In
searchconsole-mcp

searchconsole-mcp

by harisnadeem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_sitemap

Delete a sitemap from a website by providing the site URL and sitemap path. Removes the sitemap from Google Search Console.

Instructions

Delete a sitemap from a website.

Args: site_url: The site, e.g. 'https://example.com/'. feedpath: The sitemap path to delete, e.g. '/sitemap.xml'.

Returns: Empty dict on success.

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>",
      "feedpath": "<feedpath>"
    },
    "name": "delete_sitemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYes
feedpathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

Annotations are missing, so description must cover behavioral traits. It states 'delete' implying mutation, but does not disclose if the action is reversible, requires permissions, or affects other resources. Minimal disclosure beyond return value.

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?

Concise, well-structured with Args and Returns sections. Every sentence is meaningful, no 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 tool with 2 parameters and no output schema, the description adequately explains purpose, parameters, and return. Lacks behavioral context but is otherwise complete.

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

Parameters4/5

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

Schema coverage is 0%, but description adds examples and clarifies each parameter's role (site_url as the site URL, feedpath as the sitemap path). This adds value beyond the schema's type-only definitions.

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) and the resource (sitemap from a website). It distinguishes from sibling tools like get_sitemap, submit_sitemap, and list_sitemaps by the delete verb.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, such as distinguishing from submit_sitemap or list_sitemaps. Lacks context on prerequisites or consequences.

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

Deploy Server

Other Tools