Skip to main content
Glama
Sign In

ElevenLabs

by io.github.mcp-dir
OverviewDiscussionsAdmin

elevenlabs_get_voice_settings

Read-onlyIdempotent

Get Voice Settings. Returns the settings for a specific voice. "similarity_boost" corresponds to"Clarity + Similarity Enhancement" in the web app and "stability" corresponds to "Stability" slider in the web app.

Bulk support: accepts voice_ids for batched execution.

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

Input Schema

NameRequiredDescriptionDefault
accountNo
voice_idYes
voice_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context beyond that by mapping 'similarity_boost' and 'stability' to web-app sliders and confirming batch execution via voice_ids.

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 reasonably concise and front-loaded. The first sentence repeats the tool name but the remaining sentences add meaningful detail without unnecessary fluff.

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?

For a read-only tool with strong annotations and a simple schema, the description is mostly complete: it defines the purpose, the target voice, the bulk path, and two important settings mappings. The main gap is the unexplained 'account' parameter and the lack of explicit return-value detail, but no output schema is present and the tool is low complexity.

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?

Schema description coverage is 0%, so the description must compensate. It clarifies that voice_id targets a specific voice and that voice_ids enables batched execution, but the 'account' parameter remains completely unexplained.

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

Purpose4/5

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

The description clearly states 'Returns the settings for a specific voice,' giving a specific verb and resource. It does not explicitly name or contrast with sibling tools like elevenlabs_get_voice_settings_default, but 'specific voice' and 'bulk support' help narrow its role.

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?

It is implied that this tool should be used when retrieving settings for a voice, and bulk execution is mentioned. However, there is no explicit guidance on when to use this instead of the default settings getter or how it relates to editing settings.

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

All ElevenLabs toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources