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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_dubbed_transcript_file

Read-onlyIdempotent

Retrieve a dubbed project's transcript by dubbing ID and language code, with SRT, WebVTT, or JSON format. Deprecated upstream.

Instructions

Get Dubbed Transcript 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>",
      "language_code": "<language_code>"
    },
    "name": "get_dubbed_transcript_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
dubbing_idYesID of the dubbing project.
format_typeNoFormat 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/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds only the fragment 'Deprecated upstream', which vaguely signals lifecycle status but does not say whether the endpoint still returns data or what the deprecation means for the caller.

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 text is short, but it is not concise so much as incomplete and poorly formed — a sentence fragment trailing after the resource name. There is no front-loaded statement of what the tool returns or how it should be invoked.

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 3-parameter retrieval tool with no output schema, the description should at least explain what is returned (a transcript file in the requested format) and the implications of deprecation. Neither is provided, so an agent cannot confidently decide to call it.

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%: dubbing_id, language_code, and the format_type enum are all documented in the schema itself, including the 'source' convention and format meanings. The description adds no parameter meaning, so the baseline of 3 applies.

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 essentially restates the tool name ('Get Dubbed Transcript') rather than stating a distinct purpose, and the trailing fragment 'Deprecated upstream' is ungrammatical and ambiguous. It does not distinguish this tool from close siblings such as get_dubbing_transcripts, dubbing_transcript_get, or get_dubbed_file.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, when not to, or which sibling to prefer. The only guidance-adjacent text, 'Deprecated upstream', does not tell the agent whether to avoid the tool or what to call instead, leaving it unusable for routing decisions.

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