Skip to main content
Glama

seo_create_redirect

Creates a WordPress redirect with status codes and optional regex matching, while rejecting invalid patterns, unknown codes, and loops or chains deeper than five.

Instructions

Create a redirect. Rejects invalid regex, unknown status codes and redirect loops/chains deeper than 5. Returns the redirect.

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>",
      "from_url": "<from_url>"
    },
    "name": "seo_create_redirect"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
typeNoHTTP status (default 301): 301, 302, 307, 410, 451
to_urlNoTarget path or URL (required unless type is 410 or 451)
enabledNoRedirect is active (default true)
from_urlYesSource path or URL (a regex pattern without delimiters when is_regex)
is_regexNoTreat from_url as a regex (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv3.14.0
    • addedInput schema / properties / enabled
      Added value: +{
      +  "description": "Redirect is active (default true)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / from_url
      Added value: +{
      +  "description": "Source path or URL (a regex pattern without delimiters when is_regex)",
      +  "type": "string"
      +}
    • addedInput schema / properties / is_regex
      Added value: +{
      +  "description": "Treat from_url as a regex (default false)",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / redirect
      Removed value: -{
      -  "additionalProperties": {},
      -  "description": "Redirect fields (source, target, type, ...)",
      -  "type": "object"
      -}
    • addedInput schema / properties / to_url
      Added value: +{
      +  "description": "Target path or URL (required unless type is 410 or 451)",
      +  "type": "string"
      +}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "HTTP status (default 301): 301, 302, 307, 410, 451",
      +  "enum": [
      +    301,
      +    302,
      +    307,
      +    410,
      +    451
      +  ],
      +  "type": "number"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "site",
      -  "redirect"
      -]New value: +[
      +  "site",
      +  "from_url"
      +]
  2. Addedv3.4.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does add real value: it discloses validation gates (invalid regex, unknown status codes, loops/chains deeper than 5) and confirms the created redirect is returned. It still omits what happens on duplicate from_url, whether the call is idempotent, and any auth requirements — meaningful gaps for a 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.

Conciseness5/5

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

Three short sentences with the action first, then validation constraints, then return value — front-loaded and free of filler. Every sentence contributes a distinct fact.

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

Completeness4/5

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

For a 6-parameter create tool with no annotations and no output schema, the description adequately covers the operation, its rejection conditions, and its return. The remaining gap is conflict/idempotency behavior on repeat submissions, which would round out the picture.

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 every parameter (site, from_url, to_url, type, enabled, is_regex) is documented in the schema itself, including the default 301 and the regex-without-delimiters convention. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

The description opens with a specific verb+resource ('Create a redirect'), so the operation is unambiguous. It does not distinguish itself from the sibling seo_create_redirect_from_log or explain how it relates to seo_update_redirect, so the sibling-differentiation credit is missing.

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?

There is no statement of when to use this tool versus seo_create_redirect_from_log, seo_update_redirect, or seo_delete_redirect, and no prerequisites (permissions, site existence) are mentioned. The only guidance-like content is validation failure modes, which is behavior, not usage routing.

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