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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

start_speaker_separation

Initiate separation of speakers in an audio sample by supplying a voice ID and sample ID, enabling isolated speaker tracks.

Instructions

Start Speaker Separation

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": {
      "voice_id": "<voice_id>",
      "sample_id": "<sample_id>"
    },
    "name": "start_speaker_separation"
  }
}

Input Schema

NameRequiredDescriptionDefault
voice_idYesVoice ID to be used, you can use https://api.elevenlabs.io/v1/voices to list all the available voices.
sample_idYesSample ID to be used

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already indicate this is a non-read-only, open-world, non-idempotent operation, but the description adds no behavioral context such as whether it starts an async job, what permissions are needed, or what the result contains. It does not contradict the annotations, but it also adds no value beyond them.

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

Conciseness2/5

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

The description is a single short phrase, which is concise but severely under-specified. It is not wasteful, but it lacks any structure or front-loaded useful information beyond the title.

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 tool with two required parameters, no output schema, and only partial annotation coverage of behavior, the description is too thin. It omits what speaker separation produces, whether it is asynchronous, and how results are retrieved, leaving the agent under-informed.

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?

Schema coverage is 100% and both parameters are fully described in the schema. The description adds no parameter meaning, so the baseline of 3 applies because the schema already does the work.

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

Purpose2/5

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

The description simply repeats the tool name and title, 'Start Speaker Separation,' adding no specific verb-resource detail beyond the name itself. It does not distinguish this tool from siblings such as separate_song_stems, audio_isolation, or create_speaker.

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?

No guidance is provided on when to use this tool versus alternatives. The title implies a general purpose, but there are no prerequisites, exclusions, or sibling routing hints.

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