gemini-tts-mcp

Overview Schema Source Related Servers Discussions Admin

delete_voice

Remove saved Gemini TTS voices to free project slots and clear local cache. Use it when a generated voice is no longer needed or the 200-voice limit is reached.

Instructions

design_voice / generate_speech で作った保存ボイス（voice_...）を削除する。

保存ボイスはプロジェクトあたり 200 件まで（最終使用から 1 年で期限切れ）。不要になった声を削除して枠を空けるときに使う。ローカルキャッシュからも削除する。

Args: voice_id: 削除する声の ID（voice_...）。 project_id: プロジェクトID上書き（任意）。

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

Input Schema

Name	Required	Description	Default
`voice_id`	Yes
`project_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden; it discloses the 200-voice-per-project quota, the 1-year expiry from last use, and that local cache is also cleared. These are meaningful behavioral facts. It stops short of stating that deletion is permanent/irreversible or what permissions are required.

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?

Purpose is front-loaded in the first line, followed by quota context and a compact Args block. The Args section partly restates the schema but earns its place by adding format and override semantics; overall it is tight with little waste.

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 2-parameter destructive tool with an output schema (so return values need not be explained), the description covers purpose, quota context, cache side effect, and both parameters. The only notable gap is not explicitly flagging permanence/permission needs in the absence of annotations.

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 description coverage is 0%, so the description must compensate, and it does: it documents both parameters, gives the 'voice_...' format hint for voice_id, and explains project_id as an optional override. This adds real meaning beyond the bare titles in the schema.

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 (delete a saved voice 'voice_...'), and explicitly ties it to the sibling tools that create those voices (design_voice / generate_speech). An agent can distinguish this deletion tool from the creation tools without opening any 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?

Gives a clear when-to-use condition: delete unneeded voices to free a slot, in the context of the 200-per-project cap. It does not explicitly state when-not-to-use or warn about irreversibility, but the usage context is concrete rather than implied.

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

Deploy Server