Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_project

Create an ElevenLabs Studio project from a URL, document, or custom content to convert text into audiobooks and spoken audio.

Instructions

Create Studio Project Spends ElevenLabs credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the Studio project, used for identification only.
titleNoAn optional name of the author of the Studio project, this will be added as metadata to the mp3 file on Studio project or chapter download.
authorNoAn optional name of the author of the Studio project, this will be added as metadata to the mp3 file on Studio project or chapter download.
genresNoAn optional list of genres associated with the Studio project.
fictionNoAn optional specification of whether the content of this Studio project is fiction.
from_urlNoAn optional URL from which we will extract content to initialize the Studio project. If this is set, 'from_url' and 'from_content' must be null. If neither 'from_url', 'from_document', 'from_content' are provided we will initialize the Studio project as blank.
languageNoAn optional language of the Studio project. Two-letter language code (ISO 639-1).
descriptionNoAn optional description of the Studio project.
isbn_numberNoAn optional ISBN number of the Studio project you want to create, this will be added as metadata to the mp3 file on Studio project or chapter download.
source_typeNoThe type of Studio project to create.
auto_convertNoWhether to auto convert the Studio project to audio or not.
callback_urlNoA url that will be called by our service when the Studio project is converted. Request will contain a json blob containing the status of the conversion Messages: 1. When project was converted successfully: { type: "project_conversion_status", event_timestamp: 1234567890, data: { request_id: "1234567
content_typeNoAn optional content type of the Studio project.
mature_contentNoAn optional specification of whether this Studio project contains mature content.
quality_presetNoOutput quality of the generated audio. Must be one of: 'standard' - standard output format, 128kbps with 44.1kHz sample rate. 'high' - high quality output format, 192kbps with 44.1kHz sample rate and major improvements on our side. 'ultra' - ultra quality output format, 192kbps with 44.1kHz sample r
voice_settingsNoOptional voice settings overrides for the project, encoded as a list of JSON strings. Example: ["{\"voice_id\": \"21m00Tcm4TlvDq8ikWAM\", \"stability\": 0.7, \"similarity_boost\": 0.8, \"style\": 0.5, \"speed\": 1.0, \"use_speaker_boost\": true}"]
target_audienceNoAn optional target audience of the Studio project.
default_model_idNoThe ID of the model to be used for this Studio project, you can query GET /v1/models to list all available models.
from_content_jsonNoAn optional content to initialize the Studio project with. If this is set, 'from_url' and 'from_document' must be null. If neither 'from_url', 'from_document', 'from_content' are provided we will initialize the Studio project as blank. Example: [{"name": "Chapter A", "blocks": [{"sub_type": "p", "no
auto_assign_voicesNo[Alpha Feature] Whether automatically assign voices to phrases in the create Project.
from_document_pathNoAn optional .epub, .pdf, .txt or similar file can be provided. If provided, we will initialize the Studio project with its content. If this is set, 'from_url' and 'from_content' must be null. If neither 'from_url', 'from_document', 'from_content' are provided we will initialize the Studio project as
from_document_base64NoBase64 contents for "from_document". Use this when the server cannot read your local disk.
volume_normalizationNoWhen the Studio project is downloaded, should the returned audio have postprocessing in order to make it compliant with audiobook normalized volume requirements
create_publishing_readNoIf true, creates a corresponding read for direct publishing in draft state
default_title_voice_idNoThe voice_id that corresponds to the default voice used for new titles.
from_document_filenameNoFilename to send for "from_document". Some endpoints infer the audio format from it.
acx_volume_normalizationNo[Deprecated] When the Studio project is downloaded, should the returned audio have postprocessing in order to make it compliant with audiobook normalized volume requirements
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
original_publication_dateNoAn optional original publication date of the Studio project, in the format YYYY-MM-DD or YYYY.
default_paragraph_voice_idNoThe voice_id that corresponds to the default voice used for new paragraphs.
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

B3.2/5.0
Behavior3/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 one important behavioral fact beyond annotations: the operation spends ElevenLabs credits. It does not mention required permissions, rate limits, or output behavior.

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?

Extremely concise and front-loaded, with no wasted words. However, the phrasing 'Create Studio Project Spends ElevenLabs credits' is grammatically awkward and reads as two clauses fused together, slightly reducing clarity.

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?

With 31 parameters, no output schema, and rich annotations plus full schema descriptions, the description is minimally adequate. It omits when-to-use context and does not clarify what a Studio Project is or how initialization sources work, but the schema supplies those details; the main gaps are usage guidance and return expectations.

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 coverage is 100%, so all 31 parameters are fully documented in the input schema, including optional initialization sources and metadata fields. The description adds no additional parameter-level meaning beyond noting credit consumption, which is the baseline level when the schema does the heavy lifting.

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 verb ('Create') and resource ('Studio Project'), distinguishing it from broader sibling creation tools like create_audio_native_project or create_podcast. It does not explicitly contrast with the nearest sibling, edit_project, but the resource is clear enough to identify the intended action.

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?

Gives no indication of when to use this tool versus alternatives such as create_audio_native_project, create_podcast, or add_chapter. The only guidance is implicit in the tool name; no prerequisites, exclusions, or selection criteria are provided.

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