@aiwerk/mcp-server-elevenlabs

migrate_segments

Transfers dubbing segments to a different speaker within an ElevenLabs project. Spends credits; deprecated upstream.

Instructions

Move Segments Between Speakers Spends ElevenLabs credits. Deprecated upstream.

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": {
      "dubbing_id": "<dubbing_id>",
      "segment_ids": "<segment_ids>",
      "speaker_id": "<speaker_id>"
    },
    "name": "migrate_segments"
  }
}

Input Schema

Name	Required	Description
`dubbing_id`	Yes	ID of the dubbing project.
`speaker_id`	Yes
`segment_ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations cover the safety profile (non-read-only, non-idempotent, open-world), so the bar is lower. The description adds two genuinely non-obvious traits: it consumes ElevenLabs credits and is deprecated upstream, both of which materially affect whether an agent should call it.

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?

Very short and front-loaded, but the two clauses run together without punctuation ('...Spends ElevenLabs credits. Deprecated upstream.'), making the credit cost read as part of the action name. It is terse without being well-structured.

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

Completeness3/5

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

For a 3-required-param mutation tool with no output schema, the description covers cost and deprecation and annotations cover safety. However, it omits what happens to the moved segments and leaves two parameters undocumented, so it is only minimally complete.

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 only 33% (only dubbing_id documented), and the description says nothing about speaker_id or segment_ids. With two undocumented required parameters, the description fails to compensate for the coverage gap.

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?

States a specific verb and resource with scope: moving segments between speakers, which is distinct from siblings like dubbing_target_transcript_segment_update. The phrase is clear enough that an agent can identify the operation, though it does not explicitly name which sibling to prefer for segment edits.

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?

The only usage signal is 'Deprecated upstream,' which warns against use but names no replacement tool and gives no condition for when this is still appropriate. There is no guidance on when to use this versus the many other segment/dubbing tools.

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

Deploy Server