Skip to main content
Glama

dubbing_list_voices

Read-onlyIdempotent

Retrieve saved Miragea voices with their actor ID, name, and language so you can choose the right voice for a dubbing job. Read-only and supports pagination with limit and offset.

Instructions

List the voices saved in the user's Miragea account (actor_id, name, language) to use with dubbing_set_voice. Read-only.

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": "dubbing_list_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the trailing 'Read-only' adds nothing. The useful addition is the account-scoping ('user's Miragea account'), but there is no disclosure of pagination behavior or whether the list is capped, which matters for a listing tool that defaults to 50 items.

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?

One front-loaded sentence with the resource and its fields stated first, wasting very little. The only redundancy is the closing 'Read-only', which merely restates readOnlyHint from the annotations.

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?

An output schema exists, so return values need not be described, and the tool is simple (two optional params). Still, a listing tool that silently returns at most 50 items without the description mentioning pagination leaves an agent unable to know whether it has the whole voice catalog.

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?

Schema description coverage is 0% – neither 'limit' nor 'offset' carries any documentation in the schema – and the description makes no mention of pagination at all. For a low-coverage schema the description is expected to compensate, and here it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the voices saved in the user's Miragea account') and enumerates the fields returned (actor_id, name, language), which makes it trivially distinguishable from dubbing_set_voice, dubbing_list_projects, and the other siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'to use with dubbing_set_voice' implies the workflow (fetch a voice id, then assign it), which is genuine contextual guidance. However, it never states when the tool should not be used, nor does it address how to retrieve the full list when it exceeds a page.

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