redirect_bulk_deleteDelete multiple redirects at once by providing an array of redirect IDs, streamlining bulk cleanup of outdated or unwanted URL redirects.
Delete multiple redirects in bulk.
| Name | Required | Description | Default |
|---|---|---|---|
| redirect_ids | Yes |
| 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 full behavioral burden. It identifies a bulk deletion operation, but omits destructiveness warnings, permission requirements, partial-failure behavior, and any confirmation or rollback semantics.
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 front-loaded sentence with no wasted words. However, it is extremely terse for a destructive bulk operation, so its brevity borders on under-specification.
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-value details need not be explained. Yet given no annotations, 0% parameter coverage, and a destructive bulk action, the description is missing critical context about safety, usage limits, and parameter expectations.
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 0%, and the single parameter redirect_ids is not explained in the description. The description adds no meaning about ID format, source/redirect path expectations, array limits, or handling of invalid IDs beyond what the schema already shows.
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: delete multiple redirects in bulk. The word 'multiple' distinguishes it from the single-record sibling redirect_delete, but no sibling is named or contrasted explicitly.
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 on when to use this tool versus redirect_delete or other alternatives. Implied usage exists because bulk deletion is self-evident, but no exclusions, prerequisites, or routing advice are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.