Delete a stream by ID in Nginx Proxy Manager to remove unused stream forwarding entries.
Delete a stream by ID
| Name | Required | Description | Default |
|---|---|---|---|
| stream_id | Yes | The ID of the stream to delete |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Delete' signals a destructive mutation, but the definition says nothing about irreversibility, required permissions, prerequisite state (e.g., disabled), or side effects on dependent hosts.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with zero filler and the action front-loaded. Brevity is appropriate for a one-parameter tool, though the terseness arguably reflects under-specification rather than disciplined editing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive operation with no annotations and no output schema, the definition omits everything an agent needs beyond the identifier: irreversibility, error conditions, and whether dependent resources are affected. The minimal schema doesn't compensate for these gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the single parameter is already documented as 'The ID of the stream to delete'. The description's 'by ID' adds nothing beyond the schema, so the baseline 3 for high coverage applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (delete) and resource (stream), so the agent immediately knows the operation. However, it offers no differentiation from the many sibling delete tools (npm_delete_proxy_host, npm_delete_dead_host, npm_delete_access_list), relying entirely on the name to disambiguate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use or when-not-to-use guidance at all. It doesn't say whether the stream must be disabled first, whether it must have no attached hosts, or what the alternative is when deletion isn't appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.