Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_audio_native_project

Create an Audio Native project from a text or HTML article, configure its player, and optionally auto-convert the content to audio.

Instructions

Creates Audio Native Enabled Project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name.
imageNo(Deprecated) Image URL used in the player. If not provided, default image set in the Player settings is used.
smallNo(Deprecated) Whether to use small player or not. If not provided, default value set in the Player settings is used.
titleNoTitle used in the player and inserted at the top of the uploaded article. If not provided, the default title set in the Player settings is used.
authorNoAuthor used in the player and inserted at the start of the uploaded article. If not provided, the default author set in the Player settings is used.
model_idNoTTS Model ID used in the player. If not provided, default model ID set in the Player settings is used.
voice_idNoVoice ID used to voice the content. If not provided, default voice ID set in the Player settings is used.
file_pathNoEither txt or HTML input file containing the article content. HTML should be formatted as follows '<html><body><div><p>Your content</p><h3>More of your content</h3><p>Some more of your content</p></div></body></html>' Local path
text_colorNoText color used in the player. If not provided, default text color set in the Player settings is used.
file_base64NoBase64 contents for "file". Use this when the server cannot read your local disk.
auto_convertNoWhether to auto convert the project to audio or not.
file_filenameNoFilename to send for "file". Some endpoints infer the audio format from it.
sessionizationNo(Deprecated) Specifies for how many minutes to persist the session across page reloads. If not provided, default sessionization set in the Player settings is used.
background_colorNoBackground color used in the player. If not provided, default background color set in the Player settings is used.
apply_text_normalizationNoThis parameter controls text normalization with four modes: 'auto', 'on', 'apply_english' and 'off'. When set to 'auto', the system will automatically decide whether to apply text normalization (e.g., spelling out numbers). With 'on', text normalization will always be applied, while with 'off', it w
pronunciation_dictionary_locatorsNoA list of pronunciation dictionary locators (pronunciation_dictionary_id, version_id) encoded as a list of JSON strings for pronunciation dictionaries to be applied to the text. A list of json encoded strings is required as adding projects may occur through formData as opposed to jsonBody. To specif

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?

The annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, giving the safety profile for free. The description adds nothing beyond that: it does not mention that content is converted to audio, whether auto_convert triggers generation, that callers cannot retry idempotently, or that a file upload is expected.

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?

It is a single sentence with no wasted words, but it is under-specified rather than concise — the brevity comes at the cost of all useful information for a 16-parameter project-creation tool.

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?

For a complex creation endpoint with 16 parameters, a required file content field, deprecated options, and no output schema, one four-word sentence is completely inadequate. Nothing about expected inputs, the resulting project state, or follow-up steps (e.g., content update endpoints) is communicated.

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 already documents all 16 parameters including the deprecated ones and the file/file_base64/file_filename trio. The description contributes no parameter-level meaning, so the baseline 3 applies.

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?

"Creates Audio Native Enabled Project" is essentially a restatement of the tool name create_audio_native_project, with only a verb added. It gives no distinguishing detail against siblings such as add_project, create_podcast, or dubbing_project_create, so an agent cannot tell what an "Audio Native Enabled" project is or how it differs.

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 siblings like add_project and create_podcast that also create projects, the absence of any routing information is a serious gap.

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