Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

edit_project_content

Update an ElevenLabs Studio project's content using a project ID and optional URL, document, or JSON source. Initializes or replaces content; spends credits.

Instructions

Update Studio Project Content Spends ElevenLabs credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
project_idYesThe ID of the Studio project.
auto_convertNoWhether to auto convert the Studio project to audio or not.
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
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.
from_document_filenameNoFilename to send for "from_document". Some endpoints infer the audio format from it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, covering the safety profile. The description adds one genuinely useful behavioral fact not in annotations — that the operation spends ElevenLabs credits — but says nothing about whether existing content is replaced or preserved, or about prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and both ideas (purpose and credit cost) are relevant, but they are concatenated into a single ungrammatical fragment ('Update Studio Project Content Spends ElevenLabs credits.'), so the front-loading is unclear and the sentence reads awkwardly.

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 100% schema coverage and annotations carrying the safety profile, the description is minimally sufficient to invoke the tool. But for a non-idempotent mutation that consumes credits, it omits what the update actually does to existing project content and any prerequisite conditions.

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% and all seven parameters (including the content-source options from_url/from_content_json/from_document_*) are documented in the schema. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 phrase 'Update Studio Project Content' gives a verb (update) and a resource (Studio Project Content), so the general intent is recoverable. However, 'content' is left undefined against siblings like edit_project, edit_chapter, and audio_native_project_update_content_endpoint, and the run-on wording muddies the statement, so no sibling differentiation is provided.

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, when-not-to-use, or alternative routing guidance. The credit-cost note is a warning rather than usage guidance, and nothing tells the agent how this differs from edit_project or the audio-native content endpoints.

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