@aiwerk/mcp-server-elevenlabs

edit_project

Update an ElevenLabs Studio project's name, title, author, ISBN, and default voice settings. This action consumes ElevenLabs credits.

Instructions

Update Studio Project Spends ElevenLabs credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "name": "<name>",
      "default_title_voice_id": "<default_title_voice_id>",
      "default_paragraph_voice_id": "<default_paragraph_voice_id>"
    },
    "name": "edit_project"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The name of the Studio project, used for identification only.
`title`	No
`author`	No
`project_id`	Yes	The ID of the Studio project.
`isbn_number`	No
`volume_normalization`	No	When the Studio project is downloaded, should the returned audio have postprocessing in order to make it compliant with audiobook normalized volume requirements
`default_title_voice_id`	Yes	The voice_id that corresponds to the default voice used for new titles.
`default_paragraph_voice_id`	Yes	The voice_id that corresponds to the default voice used for new paragraphs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2.7/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. The description adds a useful behavioral note that this operation spends ElevenLabs credits, which is not captured in the annotations, but it omits permissions, reversibility, and side effects.

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?

The description is extremely short and front-loads the action. It is efficient, though the second clause reads as an abrupt fragment and could be integrated more clearly.

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 an 8-parameter mutation tool with no output schema, the description is incomplete. It does not explain prerequisites, how unspecified fields are handled, return behavior, or why an agent should choose this over edit_project_content.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no parameter meaning beyond the schema. With 8 parameters and 63% schema description coverage, several fields such as title, author, and isbn_number lack schema descriptions, and the tool description does not compensate for that gap.

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?

The description states a specific verb and resource: update a Studio Project. However, it does not distinguish this tool from closely named siblings such as edit_project_content, add_project, or delete_project, so sibling differentiation is missing.

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?

The description provides no guidance on when to use this tool, when not to use it, or which alternative sibling to choose. There is no usage context beyond the bare action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server