Skip to main content
Glama

seo_delete_redirect

Deletes a WordPress redirect by ID for a specified site and returns a deletion confirmation. Use it to remove obsolete or incorrect redirects from SEO settings.

Instructions

Delete a redirect by id. Returns { deleted: true }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "id": "<id>"
    },
    "name": "seo_delete_redirect"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRedirect ID
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.14.0
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
  2. Addedv3.4.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden. It usefully discloses the return payload ({ deleted: true }), but never states that deletion is permanent/irreversible, what happens when the id does not exist, or what errors are raised — critical for a destructive mutation with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, action first, return value second — no filler. It is arguably over-terse given the destructive nature, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive 2-param mutation with no annotations and no output schema, the definition omits irreversibility, failure behavior, and site scoping. Disclosing the return shape helps but does not cover what an agent needs to invoke this safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are documented there, so baseline 3 applies. The description's "by id" restates the schema and it never mentions the required site parameter or scoping, adding little beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: "Delete a redirect by id". The agent can distinguish it from seo_get_redirect, seo_update_redirect, and the post/term SEO delete siblings, though it never explicitly names those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus seo_update_redirect or the bulk/SEO delete siblings, and no preconditions (e.g. confirm the redirect exists, requires site context). Usage must be inferred entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools