Skip to main content
Glama

List Telnyx voices

list_voices
Read-only

Browse and filter available Telnyx text-to-speech voices by language, provider, or search term, with limit and offset for paging.

Instructions

Lists available Telnyx text-to-speech voices. The full catalogue has thousands of entries, so results are filtered and paged: pass language ("de"), provider ("telnyx") or a search term. Returns "returned of matched of total" plus a per-provider breakdown.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum voices to return (default 50, max 200).
offsetNoSkip this many matches (paging).
searchNoFree-text match on name, id, accent or label.
languageNoFilter by language, e.g. "de" or "de-DE".
providerNoFilter by provider, e.g. "telnyx", "aws", "elevenlabs".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only and open-world behavior, and the description adds useful context about the catalogue size, filtering, paging, and the summary return format. It still omits ordering and default behavior details, but the added context is meaningful beyond the annotations.

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 three tight sentences, front-loading the purpose and then explaining the filtering and return format. Every sentence contributes useful information with no filler.

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?

Given five optional parameters, no output schema, and read-only annotations, the description covers the essential behavior: catalogue size, filtering, paging, and return summary. Minor details such as sorting or provider defaults are omitted but not critical for correct invocation.

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 the parameters are already documented. The description repeats examples for language, provider, and search without adding much semantic detail beyond the schema, so baseline 3 is appropriate.

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 states a specific verb and resource: listing available Telnyx text-to-speech voices. It is clearly distinct from synthesis tools like speak or render_script, but it does not explicitly differentiate itself from those siblings.

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 explains that the catalogue is large and advises filtering by language, provider, or search term, which implies this is a discovery tool. However, it does not say when to use this versus alternatives or mention prerequisites or exclusions.

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