Permanently remove one ElevenLabs history item by ID, requiring explicit confirmation to prevent accidental deletion.
Permanently delete one ElevenLabs history item. Requires explicit confirm_delete=true.
| Name | Required | Description | Default |
|---|---|---|---|
| confirm_delete | No | ||
| history_item_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full burden. It does disclose the two behavioral facts that matter most for a delete tool: the effect is permanent and a confirm flag is mandatory. It stops short of covering permissions, cascade effects, or error 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?
Two short sentences, zero filler, with the destructive nature and the confirmation gate front-loaded ahead of any detail.
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 two-parameter destructive tool with no annotations and no output schema, the description covers purpose, irreversibility, and the safety gate. The gap is the undocumented identifier parameter, which leaves an agent unsure how to source a valid history_item_id.
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 0%, so the description must compensate. It adds real meaning for confirm_delete by stating the required value, but history_item_id is left entirely unexplained — no hint about its origin (e.g., from listing or getting a history item) or its format beyond maxLength 150.
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?
Uses a specific verb plus resource: "Permanently delete one ElevenLabs history item." That is enough to separate it from read-only siblings such as get_generation_history_item and download_history_audio, though it never names those alternatives explicitly.
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?
The description gives a hard precondition (confirm_delete=true), which implicitly signals this is a guarded, intentional operation. It does not say when to prefer deletion over simply ignoring an item, nor does it route the agent to list_generation_history to obtain the target id.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.