Skip to main content
Glama
Sign In
gemini-tts-mcp

gemini-tts-mcp

by tsukumonasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_voices

Retrieve available Gemini TTS voices, including saved designed voices and prebuilt options, with filters for language, gender, voice type, and keyword search plus pagination.

Instructions

使える声の一覧を返す（自分の保存ボイス → プリビルトボイスの順）。

Args: language_code: 言語で絞り込み（例: ja-JP, en-US）。 gender: 性別で絞り込み（female / male / neutral）。 voice_type: 種類で絞り込み（prebuilt / prompted / replicated）。 prompted はボイスデザインで作った声。 search: キーワード検索（例: warm, calm）。 page_size: 1 ページの件数（既定 50、最大 1000）。 page_token: 次ページ取得用のトークン（前回の next_page_token）。 project_id: プロジェクトID上書き（任意）。

Returns: voices: API から取得した声の一覧（id / display_name / type など） next_page_token: 続きがある場合のトークン designed_voices_local: この MCP がボイスデザインで作った声（説明文 → voice_id）

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
genderNo
searchNo
page_sizeNo
page_tokenNo
project_idNo
voice_typeNo
language_codeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it partially does: it discloses ordering, pagination via next_page_token, the extra designed_voices_local return field, and a project_id override. It does not state that the operation is read-only in explicit terms, nor auth/permission requirements or rate limits.

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 Args/Returns structure is easy to scan and the purpose is front-loaded in a single sentence. The Returns block partially duplicates the output schema, which is minor waste but not bloating.

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 7-parameter listing tool with no annotations, the definition covers all parameters, pagination, and the special local return field, and return values are otherwise covered by the output schema. Missing only secondary details like auth requirements and behavior on empty results.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate and largely does: it supplies accepted values for gender (female/male/neutral) and voice_type (prebuilt/prompted/replicated), explains that 'prompted' means voice-design voices, gives format examples for language_code and search, and adds a max of 1000 for page_size that the schema lacks. It stops short of fully documenting edge cases such as invalid value handling.

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?

States a specific verb+resource ('使える声の一覧を返す') and adds the ordering rule (own saved voices first, then prebuilt), which tells an agent what the list looks like. It does not explicitly contrast with siblings like design_voice or delete_voice, but the resource is unmistakable.

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 explicit when-to-use guidance, no exclusions, and no naming of alternatives (e.g., when to use list_voices vs design_voice or list_models). The ordering note is mildly informative but is not usage guidance.

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