delete_site_toolRemove a site from Google Search Console by providing its site URL. Use when you need to delete a property from your Search Console account.
Remove a site from Search Console.
| Name | Required | Description | Default |
|---|---|---|---|
| site_url | Yes | Site URL to remove |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 carries the entire burden. For a destructive removal operation it discloses nothing about reversibility, whether removal requires verification, or whether the site's data is preserved — a significant gap that could lead an agent to invoke it carelessly.
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?
A single short sentence with the action front-loaded and no filler. It is efficient, though its brevity is partly a symptom of under-specification rather than disciplined conciseness.
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?
An output schema exists so return values need not be explained, but for an irreversible, annotation-free deletion the description omits the consequences and cautions an agent needs before acting. It is too thin for the operation's risk profile.
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 site_url is fully documented in the schema itself. The description adds no format hints (e.g., URL vs. domain property prefix) or normalization behavior, so it does not exceed the baseline.
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 states a specific verb and resource ("Remove a site") and scopes it to Search Console, which is enough to distinguish it from siblings like delete_sitemap_tool. It stops short of explicitly differentiating itself from other site tools, but the purpose is unambiguous.
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 on when to use this versus list_sites_tool, get_site_tool, or delete_sitemap_tool, and no mention of prerequisites such as verifying ownership or confirming the site is unverified. The agent must infer all usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.