Remove a package version from the npm registry. Specify package and version, optionally use force for entire package, and provide OTP for two-factor authentication.
Remove a package version from the registry
| Name | Required | Description | Default |
|---|---|---|---|
| otp | No | One-time password for 2FA | |
| force | No | Force unpublish (required for entire package) | |
| package | Yes | Package name with optional version (e.g. pkg@1.0.0) |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must fully convey behavioral traits. It states the action but omits critical details like irreversibility, permission requirements, and consequences of force unpublishing an entire package.
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 succinct sentence that directly communicates the tool's purpose. No unnecessary words, though additional behavioral context could be added without sacrificing conciseness.
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?
With no output schema and a destructive action, the description fails to provide sufficient context about side effects (e.g., breaking builds), revertibility, or post-unpublish behavior. Incomplete for safe decision-making.
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?
Input schema covers 100% of parameters with clear descriptions (e.g., 'Package name with optional version'). The description adds no extra meaning, meeting the baseline for full schema coverage.
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?
The description states 'Remove a package version from the registry' with a specific verb ('Remove') and resource ('package version'), clearly distinguishing it from siblings like 'publish' or 'deprecate'.
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 tool versus alternatives like 'deprecate' (which preserves history) or when not to use it (e.g., if the package is depended upon). No explicit context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.