Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

audio_isolation_stream

Isolate vocals or speech from an audio file and return them as audio/mpeg bytes. Pass output_path to save the separated audio to disk.

Instructions

Audio Isolation Stream Spends ElevenLabs credits. Returns audio/mpeg bytes; pass output_path to save them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_pathNoThe audio file from which vocals/speech will be isolated from. 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.
audio_filenameNoFilename to send for "audio". Some endpoints infer the audio format from it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint false, openWorldHint true, idempotentHint false, destructiveHint false, giving the safety profile. The description adds useful behavior beyond annotations: it warns that the call spends ElevenLabs credits, states the return format (audio/mpeg bytes), and explains how to persist output via output_path. It does not cover auth or rate limits, but adds solid behavioral context.

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?

Two short sentences, no waste. The cost and output handling are front-loaded and easy to scan.

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 5-parameter tool with full schema coverage and annotations, the description covers cost and output handling. However, it omits the core purpose statement (isolation of vocals/speech from audio) and any distinction from sibling audio_isolation, leaving an agent to infer when to use the stream variant.

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 the baseline is 3 even without parameter details in the description. The description mentions output_path only, which the schema already fully documents; no additional parameter meaning is provided.

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

Purpose3/5

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

The description opens with "Audio Isolation Stream Spends ElevenLabs credits," which repeats the tool name and adds a cost note, but does not state a verb or what is isolated (vocals/speech from audio). The schema's audio_path description supplies the missing purpose, but the description alone lacks a clear action statement and does not distinguish from sibling audio_isolation.

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 when-to-use/when-not, no alternatives, no prerequisite context. The only contextual cue is the cost warning, which is a side effect, not usage guidance.

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