Skip to main content
Glama

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

Create a song

tempolor_create_song

Generate a song with vocals with TemPolor's current song model (more than 30 languages, up to 5 minutes) from a style prompt and your lyrics, or lyrics TemPolor writes from the prompt; for music without vocals use tempolor_create_instrumental. Optionally sung by an artist voice (tempolor_list_artist_voices) or your cloned voice (tempolor_clone_voice), or built on your MIDI file (tempolor_upload_midi): one of these at most. A track counts against the plan's monthly tracks on Lite and Pro; Ultra has no monthly count but can be limited to about 300 songs a day per account; a 429 means the accounts are busy (tempolor_list_running_jobs). Waits up to ~50 s and returns the job_id, status and, once COMPLETED, a temporary mp3 url; else call tempolor_get_music. POST /music/song.

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

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the track to finish (default true); false returns the job_id at once.
lyricsNoYour lyrics, up to 3,000 characters. Left out, TemPolor writes lyrics from the prompt.
promptYesWhat the song is: genre, mood, instruments, voice, subject. Up to 2,000 characters.
maxJobsNoThe most jobs the account may run at once for this request, from 1. Default: the account's maxJobs (tempolor_list_accounts).
user_idNoThe TemPolor account (user_id from tempolor_list_accounts) to run on. Omit to use the account that holds clonedVoiceItemId or midiItemId, else a healthy account with a free maxJobs slot.
replyRefNoYour own reference, included in every callback. Up to 1,024 characters.
replyUrlNoA callback URL that receives a POST with the job's tempolor_get_music record while the track is made and once it ends; a job not done within 60 minutes ends with code 408. Up to 1,024 characters.
midiItemIdNoA MIDI file to build the song on: a midiItemId from tempolor_upload_midi or tempolor_list_midi; the song runs on the account that holds it. Not with a voice.
model_songNoThe same values as the REST API; omit it for TemPolor's current song model. Models: https://useapi.net/docs/api-tempolor-v1#models.v4.8
artistVoiceItemIdNoAn artist voice to sing the song: an itemId from tempolor_list_artist_voices. Not with clonedVoiceItemId or midiItemId.
clonedVoiceItemIdNoYour cloned voice to sing the song: a clonedVoiceItemId from tempolor_clone_voice or tempolor_list_cloned_voices; the song runs on the account that holds it. Not with artistVoiceItemId or midiItemId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (which only declare non-readonly, non-destructive, non-idempotent, open-world), it discloses billing impact (counts against monthly tracks on Lite/Pro; Ultra ~300/day per account), the meaning of a 429, the ~50 s wait ceiling, and the temporary nature of the returned mp3 url. The only gap is that it does not restate that repeated calls create distinct jobs and consume quota each time, which matters given idempotentHint=false.

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 core purpose and the primary alternative, then layered with routing, billing, and wait semantics. It is dense but every clause carries information; the URL/endpoint tail ('POST /music/song') is the only element of marginal value to an agent.

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?

For an 11-parameter generation tool with no output schema, the description covers return values (job_id, status, temporary mp3 url), the fallback retrieval tool, latency expectations, quota cost, and error handling. Nothing an agent needs 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.

Parameters3/5

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

Schema description coverage is 100%, so every parameter including the optional voice/MIDI sources, wait, maxJobs and callback fields is already documented in the schema. The description only echoes the mutual-exclusion of voice/MIDI sources and the lyrics-or-prompt behavior, adding little beyond the structured fields; baseline 3 applies.

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?

Opens with a specific verb+resource ('Generate a song with vocals') and immediately scopes the output ('more than 30 languages, up to 5 minutes') and the inputs ('style prompt and your lyrics, or lyrics TemPolor writes'). It explicitly names the sibling for the non-vocal case (tempolor_create_instrumental), so an agent can disambiguate without opening either 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?

Gives concrete routing rules: use tempolor_create_instrumental for no vocals, tempolor_list_artist_voices for an artist voice, tempolor_clone_voice for a cloned voice, tempolor_upload_midi for MIDI, with an explicit exclusion ('one of these at most'). It also states the post-call path: call tempolor_get_music if the wait elapses, and tempolor_list_running_jobs on a 429.

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