Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

elevenlabs_list_voices

Read-onlyIdempotent

Lists all available ElevenLabs voices for selecting the right voice in text-to-speech or AI agent workflows.

Instructions

List all available voices in ElevenLabs.

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": {
      "api_key": "<api_key>"
    },
    "name": "elevenlabs_list_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.9
  2. Removed
  3. Addedv0.1.5

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety and repeatability are covered structurally. The description adds only the minor fact that all voices are returned with no filtering; it says nothing about pagination, whether results are account-scoped, or that an API key is required for auth.

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?

A single tight sentence with no filler and the core action front-loaded. It is efficient, though so terse that there is no room for the usage or auth context a caller actually needs.

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?

The tool is simple (one param, no output schema, rich annotations), so the description is close to adequate. But it omits how many voices are typically returned, whether results include metadata like voiceId/labels needed to chain into elevenlabs_text_to_speech, and the api_key requirement, which are the gaps that matter most here.

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?

Schema description coverage is 0% and the single required parameter (api_key) is completely undocumented in both schema and description. The description does not say whether the key is account-level, whether it is read from the environment, or what form it takes, so it fails to compensate for the coverage gap.

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 uses a specific verb and resource ('List all available voices') and scopes it to ElevenLabs, so an agent knows exactly what the call returns. It does not explicitly contrast with the sibling elevenlabs_get_voice (single-voice lookup) or heygen_list_voices, leaving differentiation to the names alone.

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?

There is no statement of when to use this versus elevenlabs_get_voice, elevenlabs_get_models, or elevenlabs_get_history. The only implicit cue is the word 'List', which an agent must infer means 'browse/choose a voiceId before a text-to-speech call'.

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