Skip to main content
Glama
Sign In

ElevenLabs

by io.github.mcp-dir
OverviewDiscussionsAdmin

elevenlabs_delete_finetune

Delete Music Finetune. Delete a music finetune

Bulk support: accepts finetune_ids for batched execution.

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": {
      "finetune_id": "<finetune_id>"
    },
    "name": "elevenlabs_delete_finetune"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
finetune_idYes
finetune_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior1/5

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

The description says 'Delete a music finetune', which is a destructive operation, but the annotations declare destructiveHint=false. This is a direct contradiction, so behavioral transparency must be scored as 1.

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 description is short and front-loaded, but it repeats the same idea twice: 'Delete Music Finetue' and 'Delete a music finetue'. The bulk hint is useful, but the redundancy means not every sentence earns its place.

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, multi-parameter tool with no output schema, the description is too thin. It does not mention irreversibility, account context, what happens with missing/invalid IDs, or how finetune_id relates to finetune_ids, leaving material gaps for an agent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to explain parameter meaning. It only adds context for finetune_ids ('batched execution'), but it does not explain finetune_id, account, or the relationship between single and bulk deletion.

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

Purpose4/5

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

The description clearly states the action ('Delete') and the resource ('music finetune'), so an agent can tell it deletes finetunes. It is distinguishable from sibling tools like elevenlabs_get_finetunes and elevenlabs_update_finetune, though the two opening sentences are largely redundant.

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

Usage Guidelines3/5

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

The bulk-support note provides some usage guidance: use finetune_ids for batched execution. However, it does not mention when to prefer this tool over get/update finetune tools, nor does it explain prerequisites or exclusions.

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

All ElevenLabs toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources