Request Google to remove a URL from search results when content is deleted or expired. Helps maintain accurate index.
Notify Google that a URL has been removed (e.g., expired job posting). Google only.
| Name | Required | Description | Default |
|---|---|---|---|
| siteUrl | Yes | The property URL as registered in Search Console | |
| url | Yes | The URL that was removed |
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 carry the burden. It only says 'notify Google' but does not disclose required permissions, rate limits, or whether the action is reversible or destructive.
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, compact sentence that conveys the core purpose and an example. No wasted words; front-loaded with the essential action.
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 tool with two parameters and no output schema, the description adequately covers what the tool does and its scope. No further details are necessary.
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% and parameter descriptions are clear. The tool description adds no additional meaning beyond what is already in the schema, so baseline score of 3 applies.
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 verb 'notify' and resource 'URL removal' with an example. It distinguishes itself from siblings like indexing_submit_url by focusing on removal and specifying 'Google only.'
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 indicates use when a URL is removed and is for Google only, but explicitly contrasts with Bing siblings. However, it lacks explicit when-to-use or when-not-to-use instructions relative to other indexing tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.