Nginx Proxy Manager MCP

Overview Schema Source Related Servers Discussions Admin

Delete Redirection Host

delete_redirection_host

Permanently remove a redirection host by ID from Nginx Proxy Manager, deleting its redirect configuration. Use dry_run=True to preview the irreversible change before applying it.

Instructions

Permanently delete a redirection host by ID, removing its redirect configuration from NPM. Use disable_redirection_host to retain it while stopping redirects; list_redirection_hosts helps verify the ID. Deletion cannot be undone and applies the NPM configuration change. Returns True on success. Set dry_run=True to preview the exact request without changing NPM.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	ID of the redirection host, from the matching list tool.
`dry_run`	No	When True, return the exact request preview without changing NPM.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.2Oct 16, 2026

addedInput schema / properties / dry_run / description

Added value: +"When True, return the exact request preview without changing NPM."

addedInput schema / properties / id / description

Added value: +"ID of the redirection host, from the matching list tool."

First observedv0.5.1Oct 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so richly: irreversible ('cannot be undone'), applies an NPM config change, returns True on success, and a dry_run preview mode. This is exactly the behavioral context an agent needs for a destructive mutation.

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 tightly packed sentences: action/effect front-loaded, then alternatives, then reversibility/return/preview. No filler; every clause earns its place.

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 single-resource delete with an output schema present, the description covers irreversibility, alternatives, ID sourcing, return value, and dry-run preview. Nothing an agent needs to call it correctly 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 parameters are fully documented in the schema. The description still adds value by explaining the dry_run semantics ('preview the exact request without changing NPM') and the id source, slightly above the baseline 3.

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 (delete) and resource (redirection host) with the scope clarified as 'by ID' and the effect stated precisely ('removing its redirect configuration from NPM'). Clearly distinguishable from siblings 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 Guidelines5/5

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

Explicitly names the non-destructive alternative (disable_redirection_host to retain while stopping redirects) and points to list_redirection_hosts to resolve the ID. This gives clear when-to-use-this-vs-that guidance.

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