Delete an API token by its unique ID to revoke access immediately. Requires the token ID for removal.
Delete an API token. API token required.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the token to delete |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It mentions that an API token is required, which hints at authentication, but it does not disclose that deletion is likely irreversible, what side effects occur, or whether the token is immediately invalidated.
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?
The description is extremely short and front-loaded with the core action. Both sentences earn their place, with no unnecessary elaboration.
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 simple one-parameter delete operation, this is minimally viable: the parameter is fully documented and the action is clear. However, with no annotations and no output schema, the description omits important behavioral context such as irreversibility and the result of the operation.
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?
The schema fully documents the 'id' parameter with a clear description. The tool description adds no extra semantic detail about the parameter, so it provides the baseline value but no additional value.
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 uses a specific imperative verb ('Delete') and names the exact resource ('API token'), making the action unambiguous. It is clearly distinct from sibling token operations like create_token, update_token, and get_tokens.
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 is given about when to use this tool versus alternatives, nor are any exclusions or conditions provided. The action itself implies usage, but the description does not help an agent decide between delete_token and update_token.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.