Skip to main content
Glama

delete-redirection-host

delete-redirection-host

Removes a redirection host from an Nginx Proxy Manager instance by its ID, helping clean up unused or incorrect redirects.

Instructions

Delete a redirection host by ID.

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": {
      "instanceName": "<instanceName>",
      "id": "<id>"
    },
    "name": "delete-redirection-host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 behavioral burden. It says only that a resource is deleted; it does not say whether deletion is permanent, what happens to associated records, whether dependent state must be cleared first, or what errors occur for a nonexistent ID.

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?

One short sentence with the verb and key front-loaded and no filler. Its brevity is efficient, though the same brevity leaves required context unstated.

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 mutation with no annotations, no output schema, and zero schema-level parameter documentation, the description is too thin. An agent needs at minimum what instanceName means and whether the delete is irreversible or conditional on host state.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters. The description clarifies that "id" identifies the redirection host, but the required "instanceName" parameter is never mentioned and its meaning (which instance/tenant the host lives in) is left entirely undocumented.

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 states a specific verb and resource ("Delete a redirection host") and names the lookup key ("by ID"), which is enough to distinguish it from create/disable/enable/update-redirection-host siblings by verb alone. It stops short of explicitly contrasting itself with delete-proxy-host or delete-certificate, so it is clear but not fully differentiated in prose.

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 guidance on when to use this tool versus alternatives, no precondition that the host be disabled first (notable given the sibling disable-/enable-redirection-host tools), and no warning about confirmation or irreversibility. The agent must infer all invocation context from the name.

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