Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

speech_to_speech_full

Converts source audio into a target voice using ElevenLabs speech-to-speech, returning audio/mpeg bytes or saving them to a chosen output path.

Instructions

Speech To Speech Spends ElevenLabs credits. Returns audio/mpeg bytes; pass output_path to save them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoIf specified, our system will make a best effort to sample deterministically, such that repeated requests with the same seed and parameters should return the same result. Determinism is not guaranteed. Must be integer between 0 and 4294967295.
model_idNoIdentifier of the model that will be used, you can query them using GET /v1/models. The model needs to have support for speech to speech, you can check this using the can_do_voice_conversion property.
voice_idYesVoice ID to be used, you can use https://api.elevenlabs.io/v1/voices to list all the available voices.
audio_pathNoThe audio file which holds the content and emotion that will control the generated speech. Local path. Required for this call.
file_formatNoThe format of input audio. Options are 'pcm_s16le_16' or 'other' For `pcm_s16le_16`, the input audio must be 16-bit PCM at a 16kHz sample rate, single channel (mono), and little-endian byte order. Latency will be lower than with passing an encoded waveform.
output_pathNoWhere to write the returned bytes. Relative paths resolve against ELEVENLABS_OUTPUT_DIR. Omit it to get the data inline as base64 (small files only).
audio_base64NoBase64 contents for "audio". Use this when the server cannot read your local disk.
output_formatNoOutput format of the generated audio. Formatted as codec_sample_rate_bitrate. So an mp3 with 22.05kHz sample rate at 32kbs is represented as mp3_22050_32. MP3 with 192kbps bitrate requires you to be subscribed to Creator tier or above. PCM and WAV formats with 44.1kHz sample rate requires you to be
audio_filenameNoFilename to send for "audio". Some endpoints infer the audio format from it.
enable_loggingNoWhen enable_logging is set to false zero retention mode will be used for the request. This will mean history features are unavailable for this request, including request stitching. Zero retention mode may only be used by enterprise customers.
voice_settingsNoVoice settings overriding stored settings for the given voice. They are applied only on the given request. Needs to be send as a JSON encoded string.
remove_background_noiseNoIf set, will remove the background noise from your audio input using our audio isolation model. Only applies to Voice Changer.
optimize_streaming_latencyNoYou can turn on latency optimizations at some cost of quality. The best possible final latency varies by model. Possible values: 0 - default mode (no latency optimizations) 1 - normal latency optimizations (about 50% of possible latency improvement of option 3) 2 - strong latency optimizations (abou

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, open-world operation, and the description adds genuinely useful behavioral context beyond that: it consumes ElevenLabs credits and returns audio/mpeg bytes rather than structured data. It stops short of disclosing latency, long-running behavior, or enterprise/tier constraints.

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?

Two short sentences with no filler, and the cost warning is front-loaded ahead of the output-format detail. The first sentence reads awkwardly ('Speech To Speech Spends ElevenLabs credits') but the content is efficient.

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 13-parameter generation tool with no output schema, the description covers the return type and cost, which is the right emphasis. However, it omits input requirements (voice_id required, audio_path or audio_base64 supply path) and any note on runtime or tier restrictions, leaving meaningful gaps.

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%, so all 13 parameters are already documented in the schema. The description only restates one of them (output_path for saving bytes), which is already described there, and adds nothing about voice_id, audio_path, or model_id selection.

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?

States a specific operation, 'Speech To Speech', on an audio resource, and implies it produces converted audio. It is distinguishable from the sibling speech_to_speech_stream only by the implicit 'full' vs 'stream' contrast, which the description does not spell out, so it stops short of a 5.

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?

It notes that credits are spent, which hints at a cost consideration, but gives no explicit when-to-use guidance, no conditions, and no mention of when to prefer speech_to_speech_stream or other conversion tools in the sibling list.

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