Skip to main content
Glama
Sign In
@aiwerk/mcp-server-elevenlabs

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_agent_draft_route

DestructiveIdempotent

Delete an agent draft branch by agent ID and branch ID. Removes unwanted draft revisions to keep ElevenLabs agent configurations clean.

Instructions

Delete Agent Draft

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>",
      "branch_id": "<branch_id>"
    },
    "name": "delete_agent_draft_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe id of an agent. This is returned on agent creation.
branch_idYesThe ID of the agent branch to use

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is fully covered by structured fields. The description adds no behavioral context beyond them – nothing about what a draft is, whether deletion is permanent, or any auth/permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The four-word description is efficiently front-loaded and wastes no space, but it is under-specified rather than genuinely concise – there is simply not enough content to be useful. Brevity here reflects omission, not discipline.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world delete operation with two required identifiers and no output schema, the description provides no consequential context – no explanation of scope, permanent effects, or relation to other agent-delete tools. Annotations cover safety but do not compensate for the missing task context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both required parameters (agent_id, branch_id) are fully documented in the schema at 100% coverage, so the schema carries the semantics. The description adds nothing about parameters, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource (delete + agent draft), but it is essentially the tool name restated and does not explain what an 'agent draft' is or how it differs from siblings like delete_agent_route, delete_agent_hold_audio_route, or delete_agent_test_folder_route. An agent can guess the action but cannot confidently distinguish it from the many other agent-delete variants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. Given the dense cluster of delete_*agent* siblings, the absence of any routing guidance is a notable gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools