Remove a site from Google Search Console or Bing Webmaster Tools to manage your verified properties.
Remove a site from Search Console or Bing Webmaster Tools
| Name | Required | Description | Default |
|---|---|---|---|
| siteUrl | Yes | The URL of the site to delete | |
| 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?
No annotations are provided, so the description must bear the full burden. It indicates a destructive action but does not mention side effects, permanence, or authorization requirements. Adequate but could be more transparent.
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?
Single sentence, front-loaded verb, no extraneous words. Highly concise and structured.
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 delete tool with two well-described parameters, the description is largely complete. However, missing notes on reversibility or access requirements could be added for full completeness.
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?
Schema coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema descriptions for 'engine' and 'siteUrl'.
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 'Remove a site from Search Console or Bing Webmaster Tools' clearly specifies the action (remove) and resource (site), and distinguishes from siblings like sites_add or sites_get.
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?
The description implicitly states when to use (when you need to delete a site), but lacks explicit guidance on when not to use or alternatives. Given the context, it's clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.