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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_dubbing_transcripts

Read-onlyIdempotent

Retrieve transcripts for a dubbing project by dubbing ID, language code, and format (SRT, WebVTT, or JSON) for subtitles or full text. Use 'source' to get the original media transcript.

Instructions

Retrieve A Transcript

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>",
      "language_code": "<language_code>",
      "format_type": "<format_type>"
    },
    "name": "get_dubbing_transcripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
dubbing_idYesID of the dubbing project.
format_typeYesFormat to return transcript in. For subtitles use either 'srt' or 'webvtt', and for a full transcript use 'json'. The 'json' format is not yet supported for Dubbing Studio.
language_codeYesISO-693 language code to retrieve the transcript for. Use 'source' to fetch the transcript of the original media.

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 declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond those annotations—no auth requirements, rate limits, output characteristics, or format-handling nuances.

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 four-word description is not concise but under-specified; it restates the tool name without earning its place. Brevity here reflects missing information rather than efficient structure.

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 three required parameters and many sibling transcript tools, the description omits what makes this tool distinct and when to use it. It fails to carry the contextual burden despite rich annotations and schema.

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% and the schema fully documents all three required parameters, including the format_type enum and language_code semantics. The description adds no parameter meaning, so the baseline of 3 is appropriate.

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?

"Retrieve A Transcript" restates the tool name minus 'dubbing,' adding no specific resource or scope. Among dozens of transcript-related siblings (dubbing_transcript_get, get_transcript_by_id, dubbing_target_transcript_get, etc.), the description provides no differentiation, leaving an agent unable to tell which transcript tool to select.

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 description offers no when-to-use guidance, no prerequisites, and no alternatives. With many sibling transcript tools, this absence of routing information is a clear gap.

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