Skip to main content
Glama

List voices

voices_list
Read-onlyIdempotent

List the voices available for text-to-speech. Use a voice's id as style.voice_name in the AI Voice Generator API. To fetch the next page, pass the response's next_cursor as cursor.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of voices to return. Defaults to 20.
cursorNoOpaque pagination cursor from the previous response's next_cursor.

Output Schema

NameRequiredDescriptionDefault
voicesYes
next_cursorYesCursor for the next page, or null when there are no more voices.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds real context beyond that: how the returned id is consumed and how to page through results using next_cursor, which an agent needs to behave correctly.

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?

Three short sentences, front-loaded with purpose, then the key downstream usage, then pagination. No filler or redundancy.

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 needn't enumerate return fields, and it covers the one behavioral thing that matters (pagination via next_cursor). Minor gap: it doesn't hint at what a voice record contains or mention the default page size.

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 coverage is 100%, so both parameters (limit, cursor) are already documented including defaults and bounds. The description's cursor guidance largely restates what the schema says, and it never mentions limit. Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb and resource ('List the voices available for text-to-speech') and immediately explains the downstream purpose of the returned IDs. An agent can distinguish this read-only catalog lookup from generation/creation siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly frames this as the prerequisite step for text-to-speech: take a voice's id and supply it as style.voice_name. Pagination instructions are given. It stops short of explicitly excluding alternatives or naming sibling tools, but the usage context is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources