Skip to main content
Glama
Sign In
Hostsmith MCP Server

Hostsmith MCP Server

by hostsmith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

delete_redirect

Destructive

Deletes one user redirect rule by its ID from list_redirects so that redirect stops applying; file-based rules must be changed in the deploy's _redirects file instead.

Instructions

Delete one user redirect rule by its id, from list_redirects. File rules can't be deleted this way: naming a file rule's line answers FileRule with the line. Change the deploy's _redirects instead, or switch the file rules off with switch_file_redirects. To delete several rules, use edit_redirects or set_redirects. Visitors stop being redirected within about 5 minutes.

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": {
      "siteId": "<siteId>",
      "ruleId": "<ruleId>"
    },
    "name": "delete_redirect"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleIdYesThe user rule's id, starting with `r_`.
siteIdYesThe site ID (from `list_sites`).
partitionNoData partition the site lives in. Omit to use the user's home partition.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds genuinely non-obvious behavior: naming a file rule's line returns a `FileRule` object with the line instead of deleting, and visitors stop being redirected within about 5 minutes. It does not say what a successful deletion returns or how an unknown `ruleId` is reported, which keeps it short of a 5.

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?

Front-loaded with the primary action, then exceptions, then alternatives, then the propagation note — a sensible ordering with no filler. The file-rule sentence is dense and requires a second read, but every sentence carries distinct information.

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

Completeness5/5

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

For a destructive, three-parameter tool with no output schema, the description covers the surprising non-deletion path (FileRule), the alternatives an agent should prefer, and the ~5 minute propagation window. Nothing essential to correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds provenance by tying `ruleId` to `list_redirects` and by clarifying that the id must be a user rule rather than a file-rule line, which meaningfully narrows what value to supply.

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

Purpose5/5

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

States a specific verb and resource ('Delete one user redirect rule'), scopes it to a single rule identified by an id sourced from `list_redirects`, and immediately distinguishes it from the file-rule case and from the bulk siblings. An agent can tell exactly what this tool does and does not touch.

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

Usage Guidelines5/5

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

Explicit when-not guidance: file rules cannot be deleted here, with two named alternatives (`_redirects` deploy edit or `switch_file_redirects`). It also routes the multi-delete case to `edit_redirects`/`set_redirects`, so both the single-vs-bulk and user-vs-file dimensions are resolved inline.

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