Skip to main content
Glama
Sign In
Nginx Proxy Manager MCP

Nginx Proxy Manager MCP

by VeryBigSad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_redirection_host

Removes a redirection host from Nginx Proxy Manager using its host ID. Useful for cleaning up unused or incorrect redirections.

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": {
      "host_id": "<host_id>"
    },
    "name": "delete_redirection_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idYesThe ID of the redirection host to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.14.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states the action, omitting details like whether deletion is permanent, what happens to associated data, or required permissions.

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?

The description is a single concise sentence with no superfluous words, appropriately sized for a simple delete operation.

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

Completeness3/5

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

The description is minimally complete for a basic delete with one parameter, but lacks context about side effects or differences from sibling tools like disable_redirection_host, which could confuse an AI agent.

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 coverage is 100% with a clear parameter description. The tool description adds no value beyond the schema, meeting the baseline but not exceeding it.

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?

The description clearly states the action (delete), the resource (redirection host), and the identifier (by ID), effectively distinguishing from sibling tools like disable_redirection_host.

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 tool over alternatives like disable_redirection_host. No prerequisites or context for using delete vs disabling are provided.

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