Retrieve available text-to-speech voices for dubbing. Optionally filter by language code to find matching voices for your projects.
List TTS voices available for dubbing.
Args: language_code: Optional filter (e.g. "fr", "ja-JP").
| Name | Required | Description | Default |
|---|---|---|---|
| language_code | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only operation via 'List' but does not explicitly state read-only status, nor does it mention pagination, sorting, or side effects. This leaves important behavioral traits unaddressed.
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 concise and front-loaded, stating the core purpose in the first sentence and then elaborating on the parameter. There is no unnecessary wording.
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 simple list tool with one optional parameter and an existing output schema, the description is largely complete. It explains the purpose and the parameter adequately; the output schema covers return values, so no further detail is necessary. However, it lacks mention of any authentication or rate-limit constraints, which might be expected, though these may be handled globally.
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?
The description adds meaning to the single parameter language_code by providing examples ('fr', 'ja-JP') and clarifying it is optional, which goes beyond the schema's bare type and title. Since schema coverage is 0%, this compensation is valuable.
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 the tool lists TTS voices for dubbing, using a specific verb and resource. It distinguishes itself from siblings like get_brand_voice (specific voice retrieval) and preview_voice (voice preview) by focusing on listing available voices.
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?
No guidance is provided on when to use this tool versus alternatives such as get_languages or preview_voice. The description only mentions the optional language filter without any context on selection criteria or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.