List Dubbing Projects. List the workspace's dubbing projects (cursor-paginated).
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | ||
| status | No | ||
| account | No | ||
| page_size | No | ||
| sort_direction | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description doesn't need to state safety. It adds the key behavioral trait of cursor-paginated listing, which is useful and not in annotations. However, it does not disclose any rate limiting or authentication requirements beyond what annotations imply.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, consisting of two short sentences. It front-loads the core purpose and adds the pagination detail without any waste. Every word earns its place, and it is appropriately sized for a listing tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a listing tool with 5 params and no output schema, the description provides the basic scope and pagination hint but lacks parameter details and any mention of response format. Given that the schema is sparse (no descriptions), the description could do more to flesh out the params. It's adequate but not complete, especially since pagination is only hinted at.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description carries the burden. The description only mentions 'cursor-paginated', which explains the cursor parameter's role. Other parameters (status, account, page_size, sort_direction) are left undocumented. The description could enumerate these parameters and their meanings to compensate for the schema gap, but it doesn't.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool lists the workspace's dubbing projects, with a specific verb ('List') and resource ('Dubbing Projects'). It is distinguished from siblings like 'elevenlabs_list_dubs' (which likely lists all dubs) and 'elevenlabs_dubbing_project_get' (which fetches a single project) by the explicit scope 'workspace's', though it could explicitly mention filtering by status or pagination.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is for listing dubbing projects, but it does not explicitly state when to use this over alternatives like 'elevenlabs_list_dubs' or 'elevenlabs_dubbing_project_get'. It lacks explicit exclusions or when-not-to-use guidance. Given the sibling names, some differentiation is implied by resource focus, but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
There are many tools with overlapping purposes, such as multiple voice retrieval tools (get_voice_by_id, get_voices, get_user_voices_v2, get_library_voices) and several dubbing transcript segment editors with only subtle naming differences. The inclusion of platform-level tools (authenticate, connect, marketplace) alongside ElevenLabs API tools further blurs boundaries.
Naming is highly inconsistent. Most tools have the 'elevenlabs_' prefix, but some do not (authenticate, connect, marketplace, report_bug, show_version, toolkit_info). Several tools have truncated/random suffix names (e.g., elevenlabs_dubbing_target_transcript_segmen_b565e6, elevenlabs_get_pronunciation_dictionary_ver_45baf2), and one tool is in Portuguese (elevenlabs_list_accounts). This mixture of conventions and languages makes the pattern unpredictable.
With 155 tools, the server is extremely bloated. It mixes a comprehensive ElevenLabs API surface with unrelated MCP platform tools (marketplace, authenticate, report_bug, etc.) that belong in a separate toolkit. This is a severe mismatch between the apparent purpose (ElevenLabs audio services) and the sheer number of tools.
The ElevenLabs-specific tools cover a wide range of operations (text-to-speech, voice management, dubbing, pronunciation dictionaries, Studio projects, workspace administration, order management), making it fairly complete for those domains. However, the inclusion of unrelated platform tools and the lack of a clear focus mean that an agent would have difficulty navigating this large surface, and some operations like music finetuning or speech engines appear only partially covered.