Delete a specific WordPress redirect by ID from a site. Use after listing redirects to remove outdated or unwanted URL redirects.
Delete a redirect by id.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Redirect ID | |
| site | Yes | Site id (see list_sites) |
Changes observed during successful MCP inspections.
v3.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not state whether deletion is permanent, whether the redirect is recoverable, if it requires a capability, or what happens if the id is missing. For a destructive mutation tool this is a significant gap.
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?
One short sentence that is front-loaded with the action and resource. It is efficient, though extremely terse given the destructive nature of the operation.
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 destructive redirect-deletion tool with no annotations and no output schema, the description omits permissions, irreversibility, and error behavior. It is not complete enough for an agent to call it safely without assumptions.
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 description coverage is 100%, with both 'id' and 'site' documented in the schema. The description adds nothing beyond the schema, so the baseline 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?
States a specific verb (Delete) and resource (redirect) scoped by id, which is clear on its own. It does not distinguish itself from sibling redirect tools like seo_update_redirect or seo_list_redirects, but the verb+resource pairing 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?
There is no guidance about when to use this tool versus alternatives such as seo_update_redirect, nor any prerequisites or confirmation that the id must already exist. Usage is only implied by the verb.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.