Delete an SSL certificate by ID to remove it from Nginx Proxy Manager, enabling certificate cleanup and management.
Delete an SSL certificate by ID
| Name | Required | Description | Default |
|---|---|---|---|
| certificate_id | Yes | The ID of the certificate 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 description says nothing about irreversibility, whether a certificate still referenced by a proxy host can be deleted, required permissions, or failure behavior.
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, front-loaded sentence with no filler; the destructive verb leads and the lookup key follows immediately. Nothing is wasted.
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 tool with no annotations and no output schema, the definition is too thin: an agent cannot tell whether deletion is reversible, blocked by dependents, or permission-gated. The parameter is covered, but the behavioral envelope is not.
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 fully documented as 'The ID of the certificate to delete'. The description's 'by ID' phrase adds nothing beyond the schema, so the baseline 3 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 (SSL certificate) with the lookup key (by ID), which clearly separates it from npm_list_certificates, npm_get_certificate, npm_create_certificate and npm_renew_certificate. It does not, however, explicitly name or differentiate against those siblings.
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 guidance on when to use this versus alternatives such as renew_certificate, and no prerequisites or warnings. The agent must infer that this is the irreversible removal path from the verb alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.