@aiwerk/mcp-server-elevenlabs

list_dubs

Read-onlyIdempotent

Retrieve and filter dubbing projects with options for pagination, sorting, and filtering by status, model, language, and creator.

Instructions

List Dubs

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_dubs"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	Used for fetching next page. Cursor is returned in the response.
`order_by`	No	The field to use for ordering results from this query.
`page_size`	No	How many dubs to return at maximum. Can not exceed 200, defaults to 100.
`dubbing_models`	No	Filter by dubbing model generation.
`dubbing_status`	No	What state the dub is currently in.
`order_direction`	No	The order direction to use for results from this query.
`creation_sources`	No	Filter by dubbing creation source.
`dubbing_statuses`	No	Filter by dubbing status.
`filter_by_creator`	No	Filters who created the resources being listed, whether it was the user running the request or someone else that shared the resource with them.
`target_language_codes`	No	Filter by target language code.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2.2/5.0

Behavior2/5

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

Annotations already cover the read-only, idempotent, non-destructive, and open-world safety profile. The description adds no behavioral context beyond those annotations, such as pagination behavior, filtering defaults, or access scope.

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?

The phrase is front-loaded and has no wasted words, but it is under-specified rather than appropriately concise. It omits necessary information for a tool with ten optional filtering and pagination parameters.

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 a listing tool with ten parameters and no output schema, the description is nearly empty. Annotations and the schema carry much of the burden, but the description still provides no usage context, filters overview, or scoping information.

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 all ten parameters are documented directly in the schema. The description adds no parameter meaning, which leaves it at the baseline score for high schema coverage.

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?

The description 'List Dubs' only restates the tool name and title. It does not clarify what a dub is, what is returned, or how this tool differs from siblings such as dubbing_project_list or get_dubbing_transcripts.

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?

No when-to-use guidance is provided, and no alternatives are mentioned. The agent receives no indication of when listing dubs is preferable to retrieving dubbing resources or transcripts.

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

Deploy Server