Skip to main content
Glama

voices

Idempotent

List ElevenLabs account voice profiles with IDs and descriptions, then optionally pick one to set the film’s speak voice; read-only unless selecting a voice, which adds one undo step.

Instructions

List the ElevenLabs voices in the person's own account (id, name, what it sounds like), read-only. With pick: a voice id becomes the film's voice for speak (one undo step). Needs ElevenLabs connected (see generator_account). Making voices costs characters: that's speak.

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

Input Schema

NameRequiredDescriptionDefault
pickNoA voice id from the list to make it the film's voice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / pick / description
      Added value: +"A voice id from the list to make it the film's voice."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations, the description discloses the mutation that occurs when pick is supplied, notes that it is one undo step, states that listing is read-only, and names the ElevenLabs connection prerequisite. It also clarifies that voice creation is not this tool's job and instead belongs to speak. This is strong behavioral context for a tool whose annotations otherwise only indicate non-read-only, idempotent, and non-destructive behavior.

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 compact and front-loads the main listing behavior before covering pick and prerequisites. A few phrases are terse or slightly awkward, such as 'Making voices costs characters: that's speak,' but there is little wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the description covers the return fields informally, the optional mutation path, the undo behavior, the connection prerequisite, and the relevant alternative tool. It is complete enough for an agent to call correctly without needing more structured output or annotation detail.

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

Parameters4/5

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

The schema already documents pick with 100% coverage, so the baseline is 3. The description adds meaningful detail beyond the schema by explaining that pick takes a voice id from the list, that it becomes the film's voice for speak, and that doing so creates one undo step.

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?

The description states a specific verb and resource: list ElevenLabs voices in the person's own account, including id, name, and sound description. It also clearly distinguishes the optional pick action and routes voice creation to the sibling speak tool, so an agent can tell what this tool does and what it does not do.

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

Usage Guidelines4/5

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

It gives clear usage context: use this to list voices, optionally pass a voice id to make that voice the film's voice, and use speak for making voices because that costs characters. It also points to generator_account for connection requirements. It lacks an explicit statement of when not to use this tool, but the alternatives are clear enough.

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