Skip to main content
Glama
Sign In
elevenlabs-mcp

elevenlabs-mcp

by neomorrison
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_voice

Retrieve full details and settings for a specific voice by providing its voice ID. Returns the voice object as JSON.

Instructions

Get full details for a single voice, including its settings.

Args: voice_id: the voice id.

Returns the voice object as JSON.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "voice_id": "<voice_id>"
    },
    "name": "get_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
voice_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden. It states that the tool returns the voice object as JSON, but omits behavioral traits like whether it is read-only, requires authentication, or what happens if the voice_id does not exist.

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 very concise with only two sentences and an Args section. Every sentence is necessary and the structure is front-loaded with purpose, making it efficient.

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?

Given the tool has an output schema, the return format is covered. However, the description does not mention error handling, missing voice_id scenarios, or authentication requirements. For a simple get tool, it is adequate but not fully complete.

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?

With 0% schema description coverage, the description must compensate. It only says 'voice_id: the voice id.', which adds minimal meaning beyond the parameter title. It does not explain what a voice is or how to obtain the ID.

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 clearly states 'Get full details for a single voice', using a specific verb and resource. It distinguishes itself from sibling tools like list_voices (list) and clone_voice (clone), making its purpose unambiguous.

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 guidance is provided on when to use this tool versus alternatives such as list_voices or get_history_item. There is no mention of prerequisites, when not to use, or context for invocation.

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