Skip to main content
Glama
veniceai

Venice MCP Server

Official
by veniceai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Venice Voice Clone / List

venice_voice_clone

Clone a text-to-speech voice by uploading an audio sample, or list available TTS voices. Returns a handle to use with the same model for synthesized speech.

Instructions

Discover or clone TTS voices. Action 'list' reads live per-model voice metadata from auth-free GET /v1/models?type=tts. Action 'create' requires sample_url, then uploads the sample to POST /v1/audio/voices for the chosen cloning model. Cloned voices come back as a vv_<id> handle; pass it as venice_tts voice together with the same model. Supports x402 wallet auth (no Venice account needed) and API key.

Input Schema

NameRequiredDescriptionDefault
modelNoTTS model the cloned voice is paired with (action=create). Defaults to tts-chatterbox-hd.
actionYeslist = fetch live TTS model voice metadata; create requires sample_url
sample_urlNoRequired for action=create. Audio sample URL; tts-chatterbox-hd accepts MP3/WAV/FLAC/M4A, tts-minimax-speech-02-hd MP3/WAV only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • changedInput schema / properties / action / description
      Previous value: -"list = show built-in voices, create = clone from sample_url"New value: +"list = fetch live TTS model voice metadata; create requires sample_url"
    • changedInput schema / properties / model / description
      Previous value: -"Voice cloning model. Required for action=create. Examples: tts-chatterbox-hd, tts-minimax-speech-02-hd."New value: +"TTS model the cloned voice is paired with (action=create). Defaults to tts-chatterbox-hd."
    • addedInput schema / properties / model / enum
      Added value: +[
+  "tts-chatterbox-hd",
+  "tts-minimax-speech-02-hd"
+]
    • changedInput schema / properties / sample_url / description
      Previous value: -"Audio sample URL for action=create. WAV/MP3/M4A."New value: +"Required for action=create. Audio sample URL; tts-chatterbox-hd accepts MP3/WAV/FLAC/M4A, tts-minimax-speech-02-hd MP3/WAV only."
  2. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only give generic flags (readOnly=false, destructive=false, idempotent=false). The description adds real behavioral context beyond them: the list action is auth-free, the create action hits POST /v1/audio/voices, the return is a `vv_<id>` handle, and both x402 wallet auth and API key are supported. It omits irreversibility/cost of cloning and any rate-limit detail.

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?

Front-loads the purpose in the first clause, then walks action-by-action, then downstream usage, then auth. Dense but every sentence is functional; a slight trim of endpoint detail would tighten it further.

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 two-action tool with no output schema, the description covers both actions, the auth model, and the create return handle. The 'list' return is only described loosely ('live per-model voice metadata'), so a consumer still guesses at the shape, but nothing needed to call it is missing.

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 100% so the baseline is 3, but the description adds a non-obvious semantic constraint absent from the schema: the cloned voice must be paired with the SAME model, and it reiterates sample_url's action-scoped requirement. That pairing rule is the kind of guidance the schema cannot express.

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+resource ('Discover or clone TTS voices') and then disambiguates its two internal actions with distinct verbs ('list' reads metadata, 'create' uploads a sample). An agent can distinguish this from venice_tts or venice_list_models without opening a 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?

Explicitly ties each action to its precondition ('create requires sample_url') and closes the loop by telling the agent to pass the returned handle to venice_tts with the same model. It names a related sibling but stops short of stating when NOT to use this tool versus venice_list_models.

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