Delete a sitemap from Google Search Console or Bing Webmaster Tools to manage search engine indexing and sitemap submissions.
Delete a sitemap from Search Console or Bing Webmaster Tools
| Name | Required | Description | Default |
|---|---|---|---|
| siteUrl | Yes | The URL of the site | |
| feedpath | Yes | The URL of the sitemap | |
| engine | No | The search engine (default: google) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description labels the action as 'Delete' but does not disclose any behavioral traits beyond that. Without annotations, it should detail side effects (e.g., irreversibility, permission requirements, behavior on missing sitemaps). The current text is insufficiently transparent for a destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that directly conveys the tool's purpose. No extraneous words or redundant information; it earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 3-parameter tool, the description is minimally adequate. However, it lacks behavioral transparency and usage guidance, which are important for a destructive action. The absence of output schema is mild, but the gaps prevent a higher score.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers all three parameters with descriptions, achieving 100% coverage. The description adds no extra meaning beyond the schema, so the baseline score of 3 applies. No additional semantic value is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (delete a sitemap) and the target platforms (Search Console or Bing Webmaster Tools). It distinguishes itself from the Bing-specific sibling bing_sitemaps_delete by implying cross-engine support via the 'engine' parameter, although this could be more explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like sitemaps_submit or the Bing-specific sitemaps_delete. The description lacks context for selection, leaving the agent to infer usage without explicit direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.