Skip to main content
Glama

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

List cloned voices

tempolor_list_cloned_voices
Read-onlyIdempotent

List the voices cloned on one TemPolor account (tempolor_clone_voice or the TemPolor web app): clonedVoiceItemId (pass it to tempolor_create_song), name, status, the voice sample in vocalUrl, createTime and the rest of TemPolor's record. Pages: pass the cursor of the answer while hasNext is true. TemPolor's ready-made voices are in tempolor_list_artist_voices. GET /music/cloned-voices.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoThe cursor of the previous page, to read the next one. Omit for the first page.
user_idNoThe TemPolor account (user_id from tempolor_list_accounts) to list. Required when you have several TemPolor accounts; with one it may be left out.

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?

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds real value beyond them: it discloses the field set returned (clonedVoiceItemId, name, status, vocalUrl, createTime) and the cursor/hasNext pagination loop, which matters because there is no output schema. It does not cover auth or account-scoping edge cases beyond the user_id note.

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?

Dense but front-loaded: purpose first, then returned fields, then pagination, then the sibling alternative, then the endpoint. The middle sentence runs long and packs several ideas into one clause chain, but nothing is redundant.

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?

Complete for a read-only list tool with no output schema: an agent learns what is listed, which fields come back, how to identify items for downstream calls, how to page, which sibling to use instead, and the underlying endpoint. Nothing needed to call it correctly 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. The description adds behavior the schema cannot: the pagination loop should continue while hasNext is true, and cursor is described as coming from the answer. It also restates the multi-account condition for user_id, which the schema already covers.

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 ('List the voices cloned on one TemPolor account'), names the two ways voices get created, and enumerates the returned fields including clonedVoiceItemId. It also explicitly separates itself from tempolor_list_artist_voices by calling those 'ready-made voices'.

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?

Gives concrete when-to-use routing: use this for cloned voices, use tempolor_list_artist_voices for TemPolor's ready-made voices. It also names the downstream consumer (pass clonedVoiceItemId to tempolor_create_song) and the pagination condition ('pass the cursor of the answer while hasNext is true').

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