Skip to main content
Glama
Sign In
elevenlabs-mcp

elevenlabs-mcp

by neomorrison
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

download_history_audio

Retrieve audio from a history item and save it to a file. Returns the absolute file path.

Instructions

Download the audio for a history item and save it to a file.

Args: history_item_id: the history item id. 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": {
      "history_item_id": "<history_item_id>"
    },
    "name": "download_history_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
history_item_idYes
output_filenameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The description discloses that it saves to a file and returns the absolute path, but since no annotations are provided, the description carries full burden. It lacks details on side effects (e.g., file overwrites), error cases, or permissions required.

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 with no superfluous text. It uses a structured docstring format with Args and Returns sections, making it easy to parse.

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?

For a simple two-parameter tool, the description covers the basic operation and return value. However, it lacks details like file format, handling of missing history items, and potential side effects, which would make it more complete.

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 description coverage is 0%, so the description must add meaning. It provides brief explanations: 'history_item_id: the history item id' and 'output_filename: optional output file name', but does not specify default behavior if output_filename is null or format constraints.

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 description clearly states 'Download the audio for a history item and save it to a file', specifying the verb, resource, and action. It distinguishes from siblings like 'download_dubbed_audio' and 'text_to_speech' by focusing on history item audio.

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?

No guidance on when to use this tool versus alternatives, such as 'download_dubbed_audio' or 'speech_to_text'. No prerequisites (e.g., history item must exist) or exclusions are mentioned.

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