Skip to main content
Glama

TemPolor MCP Server by useapi.net (third-party)

Clone a voice

tempolor_clone_voice

Clone a voice from your audio sample (MP3, WAV, M4A or FLAC, up to 50 MB through this server) and save it on a TemPolor account; for a ready-made voice use tempolor_list_artist_voices. Returns clonedVoiceItemId, to pass to tempolor_create_song (the song then runs on that account). TemPolor keeps up to 4 cloned voices on Lite, 10 on Pro and 50 on Ultra and refuses more (tempolor_delete_cloned_voice frees one). A clone not ready in time answers its clonedVoiceItemId with a message: tempolor_list_cloned_voices shows it once ready. If the call is cut off, the voice may be listed without the given name (the rename runs after the clone): check tempolor_list_cloned_voices before uploading again. POST /music/cloned-voices.

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": {
      "name": "<name>"
    },
    "name": "tempolor_clone_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public https URL of the voice sample.
nameYesA name for the cloned voice.
user_idNoThe TemPolor account (user_id from tempolor_list_accounts) to save the voice on. Required when you have several TemPolor accounts; with one it may be left out.
mimeTypeNoThe file's type. Required with contentBase64. With url the default is the url's answer, else its file extension.
contentBase64NoThe voice sample's content, base64-encoded (instead of url; small files).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (non-read-only, non-destructive, open-world, non-idempotent), the description discloses quota ceilings per plan tier, the refusal behavior when exceeded, asynchronous readiness, and a partial-failure mode where the clone lands without the requested name. That is substantial context an agent could not infer from the annotation flags; only a note on authentication specifics is absent.

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-loaded with the action, then alternatives, then return value, then quotas and edge cases — a sensible order with no filler sentences. It is dense and slightly run-on with parentheticals, and the trailing 'POST /music/cloned-voices' adds little for an agent, costing it the top score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden and does so: it names the returned clonedVoiceItemId and its downstream use in tempolor_create_song, plus the async/partial-failure case. Quota, recovery, and follow-up tooling are all covered for a 5-parameter mutation.

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 already 100%, so the baseline is 3; the description adds the 50 MB upload cap and the accepted audio formats that are not stated in the schema, plus implicit scoping of user_id via 'save it on a TemPolor account'. It still doesn't explain the interplay between url and contentBase64 at any depth beyond what the schema says.

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 — 'Clone a voice from your audio sample ... and save it on a TemPolor account' — and immediately contrasts with tempolor_list_artist_voices for ready-made voices. An agent can distinguish this from every sibling 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 Guidelines5/5

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

Explicitly routes the agent: use tempolor_list_artist_voices for prebuilt voices, use this tool to clone your own sample, and use tempolor_delete_cloned_voice when a quota is hit. It also gives recovery guidance ('check tempolor_list_cloned_voices before uploading again') for the interrupted-call case.

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