Skip to main content
Glama
Sign In
elevenlabs-mcp

elevenlabs-mcp

by neomorrison
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

download_dubbed_audio

Retrieve the dubbed audio file from a completed dubbing job by providing the job ID and target language code.

Instructions

Download the dubbed audio for a completed dubbing job.

Args: dubbing_id: the dubbing job id. language_code: the target language code to download. output_filename: optional output file name.

Returns the absolute path of the saved audio file.

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": "download_dubbed_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
dubbing_idYes
language_codeYes
output_filenameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It states the return value ('absolute path of the saved audio file') and the action. It does not disclose permissions or side effects, but for a download tool this is reasonable.

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

Conciseness5/5

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

The description is very concise, using bullet points for parameters and a clear statement of the return value. No unnecessary words.

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

Completeness4/5

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

Given the tool's simplicity, the description covers key aspects: what it does, parameters, and return. It could mention that the dubbing job must be complete and the file format, but overall it is complete enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates by explaining each parameter: dubbing_id, language_code, and output_filename. Agents can understand their meaning without schema hints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool name and description clearly specify the action (download) and resource (dubbed audio for a completed dubbing job). It distinguishes itself from siblings like 'download_history_audio' and 'dub_audio' by focusing on dubbed audio output.

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 implies the dubbing job must be completed ('for a completed dubbing job') but does not explicitly state when to use this tool versus alternatives or provide conditions or prerequisites.

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