Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

edit_voice

Update an existing ElevenLabs voice by editing its name, labels, description, and sample files. Use it to modify voice metadata or add audio samples for cloning.

Instructions

Edit Voice

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name that identifies this voice. This will be displayed in the dropdown of the website.
labelsNoLabels for the voice. Keys can be language, accent, gender, or age.
voice_idYesVoice ID to be used, you can use https://api.elevenlabs.io/v1/voices to list all the available voices.
descriptionNoA description of the voice.
files_pathsNoAudio files to add to the voice Local paths.
files_filenamesNoFilenames to send for "files". Some endpoints infer the audio format from them.
files_base64_listNoBase64 contents for "files", one entry per file. Use this when the server cannot read your local disk.
moderate_metadataNoRun synchronous LLM moderation over the voice name and description when they change. Has no effect unless the voice_library_metadata_moderation feature flag is enabled for the user.
remove_background_noiseNoIf set will remove background noise for voice samples using our audio isolation model. If the samples do not include background noise, it can make the quality worse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note on which fields are mutated, whether omitted fields are preserved, or that files_paths/files_base64_list upload audio into an existing voice.

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?

Two words with zero waste but also zero substance. This is under-specification rather than conciseness, matching the calibration case for a name-only description.

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

Completeness1/5

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

A nine-parameter mutation tool with file-upload and moderation side effects, no output schema, and many overlapping voice siblings needs far more than a two-word description. Nothing an agent needs in order to call it safely or correctly is present.

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 schema itself documents all nine parameters (name, labels, voice_id, description, files_paths, files_filenames, files_base64_list, moderate_metadata, remove_background_noise). Per the high-coverage baseline, 3 is correct even though the description contributes no parameter meaning.

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?

"Edit Voice" is a bare restatement of the tool name/title and gives no more information than the identifier already does. It does not state what aspect of the voice is edited, what the required voice_id+name pair implies, or how it differs from siblings like edit_voice_settings, edit_pvc_voice, or update_speaker.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 prerequisites, and no mention of alternatives. With ~40 voice-related siblings (add_voice, create_voice, delete_voice, edit_pvc_voice, edit_voice_settings, get_voice_by_id), an agent has no basis for choosing this tool.

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