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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

dubbing_transcript_segment_add

Insert a new segment into a dubbing project transcript with text, speaker, and start/end times. This call spends ElevenLabs credits.

Instructions

Add Dubbing Transcript Segment Spends ElevenLabs credits.

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>",
      "text": "<text>",
      "speaker_id": "<speaker_id>",
      "start_s": "<start_s>",
      "end_s": "<end_s>"
    },
    "name": "dubbing_transcript_segment_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text of the new segment.
end_sYesEnd time of the segment, in seconds.
start_sYesStart time of the segment, in seconds.
project_idYesIdentifier of the dubbing project.
speaker_idYesIdentifier of the segment's speaker.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-idempotent, non-destructive, open-world write operation. The description adds a meaningful behavioral trait not in annotations: it spends ElevenLabs credits. However, it does not describe validation, duplicate handling, or what the tool returns, so it is useful but not rich.

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 a single front-loaded sentence with no wasted words. It is slightly awkward as a run-on ('Add Dubbing Transcript Segment Spends ElevenLabs credits'), but both clauses earn their place by covering the action and the cost.

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?

With full schema coverage and annotations covering the write safety profile, the description only needs to add contextual value. It does add the credit cost, but it omits prerequisites such as needing an existing project and speaker, and does not clarify that this adds rather than replaces segments. It is minimally viable but thin.

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 description coverage is 100%, with each of the five required parameters clearly described. The description adds no further parameter meaning, so the baseline of 3 is appropriate because the schema already carries the full parameter burden.

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 gives a specific verb and resource ('Add Dubbing Transcript Segment'), so an agent knows it creates a new transcript segment. It does not explicitly differentiate from sibling tools like dubbing_transcript_segment_update or dubbing_transcript_segment_delete, so it is clear but lacks sibling routing.

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 guidance is the cost side effect ('Spends ElevenLabs credits'), which implies use should be deliberate, but there is no when-to-use condition, when-not-to-use condition, or mention of alternatives such as update or delete. The agent must infer usage entirely from the name.

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