Skip to main content
Glama
Sign In
elevenlabs-mcp

elevenlabs-mcp

by neomorrison
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_voices

Retrieve a JSON summary of all voices available in your ElevenLabs account, with optional search filtering by name or labels.

Instructions

List the voices available in your account.

Args: search: optional case-insensitive substring to filter by name/labels.

Returns a JSON summary of each voice (id, name, category, labels).

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_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so the description must cover behavior. It states the tool lists voices and returns a JSON summary with specific fields, but lacks details on side effects, rate limits, or pagination. Adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with the main purpose, then parameter details, then return format. No redundant words.

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

Completeness4/5

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

With an output schema present, the description still usefully lists returned fields. Missing pagination or limit details, but otherwise complete for a basic list tool given the context of many siblings.

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 'search' parameter is described as case-insensitive and filtering by name/labels, adding clear meaning beyond the schema (which only defines type). This compensates for the 0% schema description coverage.

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 uses the specific verb 'List' and resource 'voices' with clear scope 'in your account'. It distinguishes from siblings like 'get_voice' (single) and 'search_voice_library' (broader search).

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 description implies usage for listing all account voices or filtering by search, but it does not explicitly state when to avoid using it or compare with sibling tools like 'search_voice_library'. Guidance is minimal.

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

Deploy Server

Other Tools