Skip to main content
Glama

get_voice

Retrieve detailed information about a specific ElevenLabs voice using its unique voice ID for text-to-speech applications.

Instructions

Get details of a specific voice

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voice_idYes

Implementation Reference

  • The handler function for the 'get_voice' tool. Decorated with @mcp.tool for registration. Fetches voice details via ElevenLabs client API and returns a structured McpVoice object.
    @mcp.tool(description="Get details of a specific voice")
    def get_voice(voice_id: str) -> McpVoice:
        """Get details of a specific voice."""
        response = client.voices.get(voice_id=voice_id)
        return McpVoice(
            id=response.voice_id,
            name=response.name,
            category=response.category,
            fine_tuning_status=response.fine_tuning.state,
        )
  • Pydantic BaseModel defining the output schema for the get_voice tool, including voice id, name, category, and fine_tuning_status.
    class McpVoice(BaseModel):
        id: str
        name: str
        category: str
        fine_tuning_status: Optional[Dict] = None
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves details, implying a read-only operation, but does not cover aspects like authentication requirements, rate limits, error handling, or response format. This is inadequate for a tool with no annotation coverage, leaving key behavioral traits unspecified.

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 a single, efficient sentence that is front-loaded and wastes no words. It directly states the tool's purpose without unnecessary elaboration, making it appropriately sized for its simplicity. Every part of the sentence earns its place by conveying the core function.

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

Completeness2/5

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

Given the tool's complexity (a read operation with one parameter) and the lack of annotations and output schema, the description is incomplete. It does not specify what details are returned, error conditions, or how it differs from sibling tools. This leaves significant gaps for an AI agent to understand and use the tool effectively.

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

Parameters3/5

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

The description adds minimal meaning beyond the input schema. It implies the 'voice_id' parameter is used to identify a specific voice, but with 0% schema description coverage, it does not explain what a voice ID is, its format, or how to obtain it. Since there is only one parameter, the baseline is 4, but the lack of compensation for the coverage gap reduces the score.

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

Purpose3/5

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

The description states the tool's purpose ('Get details of a specific voice'), which is clear but vague. It specifies the verb ('Get') and resource ('voice'), but does not differentiate from siblings like 'search_voice_library' or 'search_voices', nor does it clarify what 'details' entail. This leaves the scope ambiguous compared to similar tools.

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. The description does not mention prerequisites, such as needing a specific voice ID, or contrast it with sibling tools like 'search_voices' for broader queries. Usage is implied only by the tool name and description, with no explicit context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/projectservan8n/elevenlabs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server