Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

compose_detailed

Generates music with full control over prompt, lyrics, style, model, and output format, returning a detailed response while consuming ElevenLabs credits.

Instructions

Compose Music With A Detailed Response Spends ElevenLabs credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNo
promptNo
model_idNo
finetune_idNo
lyrics_textNo
music_promptNoComposition plan for the `music_v1` model. Using this field with any other model will result in an error.
output_formatNoOutput format of the generated audio. Formatted as codec_sample_rate_bitrate. Use "auto" (the default) to let the API pick the best format for the selected model: mp3_44100_128 for v1 models and mp3_48000_192 for v2 models.
sign_with_c2paNoWhether to sign the generated song with C2PA. Applicable only for mp3 files.
generation_modeNo
music_length_msNo
with_timestampsNoWhether to return the timestamps of the words in the generated song.
composition_planNo
finetune_strengthNoHow strongly the finetune influences the generation. Defaults to 1.0 (full strength). Lower values soften the influence of the finetune, leaving more room for prompt-level steering. Only meaningful when `finetune_id` is also provided.
force_instrumentalNoIf true, guarantees that the generated song will be instrumental. If false, the song may or may not be instrumental depending on the `prompt`. Can only be used with `prompt`.
model_style_prefixNo
use_phonetic_namesNoIf true, proper names in the prompt will be phonetically spelled in the lyrics for better pronunciation by the music model. The original names will be restored in word timestamps.
store_for_inpaintingNoWhether to store the generated song for inpainting.
with_waveform_visualNoWhether to return the visual waveform of the generated song.
respect_sections_durationsNoControls how strictly section durations in the `composition_plan` are enforced. Only used with `composition_plan` and only applies to `music_v1`; for `music_v2` and `music_v2_5` section durations are always enforced and this is ignored. When false for `music_v1`, the model may adjust individual sect

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so safety and idempotency are covered. The description's one extra fact – that it spends ElevenLabs credits – is genuinely useful beyond the annotations, though thin. It says nothing about latency, rate limits, or auth.

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 single run-on sentence is short but poorly structured and mixes purpose with a cost note without punctuation. It is under-specification rather than effective conciseness, and not front-loaded with the key distinguishing behavior.

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 19-parameter music-generation tool with no output schema and complex nested inputs like music_prompt and composition_plan, the description is drastically incomplete. It omits model selection guidance, the music_v1-only constraint of music_prompt, and any notion of what 'detailed response' returns.

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 53%, and the description itself mentions no parameters. For the roughly half of parameters that lack schema descriptions (seed, prompt, lyrics_text, generation_mode, music_length_ms, etc.), the description provides no compensating detail. Baseline 3 fits a mid-coverage schema with no param info in the description.

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 'Compose Music With A Detailed Response Spends ElevenLabs credits' restates the title and adds only a vague cost note. It doesn't specify what 'detailed response' means or how this differs from siblings like compose_plan, stream_compose, or compose_detailed_stream, which all involve music composition.

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?

There is no when-to-use guidance, no alternatives mentioned, and no preconditions stated. An agent cannot tell from this description when to choose compose_detailed over compose_plan or compose_detailed_stream.

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