ElevenLabs

elevenlabs_dubbing_transcript_segment_update

Update Dubbing Transcript Segment. Enterprise only. Edit a source segment's text, speaker, or timing.

Bulk support: accepts project_ids, segment_ids, speaker_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": {
      "project_id": "<project_id>",
      "segment_id": "<segment_id>"
    },
    "name": "elevenlabs_dubbing_transcript_segment_update"
  }
}

Input Schema

Name	Required	Description	Default
`text`	No
`end_s`	No
`account`	No
`start_s`	No
`project_id`	Yes
`segment_id`	Yes
`speaker_id`	No
`project_ids`	No
`segment_ids`	No
`speaker_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The description aligns with annotations by framing the operation as a mutation ('Update', 'Edit'). It adds useful behavioral context such as the enterprise-only restriction and batched execution support. However, it does not disclose what happens to omitted fields, the meaning of null values, or whether bulk updates are atomic or partial.

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

Conciseness4/5

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

The description is short and front-loaded: the core action is stated first, then the enterprise restriction, then editable fields, then bulk support. The first sentence is somewhat redundant with the tool name but the overall text is efficient and free of unnecessary detail.

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?

Given 10 parameters, no output schema, and no parameter-level schema documentation, the description is too thin. It omits important context such as expected return values, partial-update behavior, null-field handling, and how the bulk parameters interact with the required singular parameters.

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 coverage is 0%, so the description must compensate. It identifies the editable fields (text, speaker, timing) and mentions bulk array parameters, but leaves several parameters unexplained, including 'account', the relationship between singular and plural parameters, and null-value semantics. For 10 parameters, this is insufficient.

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 tool updates a dubbing transcript segment and specifies the editable aspects: text, speaker, or timing. The phrase 'source segment' helps differentiate from target-transcript segment siblings, though it does not explicitly identify the closely named 'elevenlabs_dubbing_transcript_segments_update' sibling.

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 description provides some usage context: it is enterprise-only, edits source segments, and supports bulk execution via arrays. However, it does not explain when to use this tool versus the plural 'segments_update' sibling or the target-transcript segment tools, leaving the agent without explicit alternative-selection guidance.

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

All ElevenLabs tools Inspect

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.