Skip to main content
Glama

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

Get a track's download link

tempolor_download_music
Read-onlyIdempotent

A temporary download link for a COMPLETED song or instrumental (job_id): mp3 (default) or wav as url with remainSeconds (the link expires after that many seconds), or stems as stemsZipUrl, a ZIP of the separated vocals and instruments, which TemPolor makes on request (the API waits up to 60 s for it; the ZIP can take about a minute to prepare, so the first call may time out, and calling again starts the preparation again). A track still generating answers 400 with its status; 404 Music file information not available right after COMPLETED means not yet, ask again in a few seconds. For your own audio file use tempolor_split_stems. GET /music/download/{job_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": {
      "job_id": "<job_id>"
    },
    "name": "tempolor_download_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id of a COMPLETED track, e.g. user:12345-tempolor:<user_id>-job:<itemId> (it names the account).
file_formatNomp3 (default), wav, or stems (a ZIP).mp3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds a lot beyond them: the link's expiry via remainSeconds, the up-to-60s server wait for stems, the possibility of a first-call timeout, and error-code semantics. The one friction point is that "calling again starts the preparation again" sits slightly against the idempotent hint, though it describes a retry cost rather than a state change, so it is not a contradiction.

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 outcome, and nearly every clause carries operational detail an agent needs. It is a single dense run-on sentence with stacked parentheses, which hurts scanability, but little could be cut without losing retry or timing guidance.

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?

With no output schema, the description still names the return fields (url, remainSeconds, stemsZipUrl) and explains the failure modes and their timing. That is nearly everything an agent needs to call and interpret the result; only pagination or exact error payload shape is absent, which is minor.

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, but the description adds genuine meaning: it explains that file_format=stems yields a ZIP of separated vocals and instruments prepared on request, and it calls out mp3 as the default. That goes beyond the terse enum descriptions 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 (temporary download link for a COMPLETED song or instrumental) and enumerates the exact forms the result can take (mp3/wav url with remainSeconds, or stemsZipUrl). This is distinguishable at a glance from siblings like tempolor_get_music or tempolor_split_stems.

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 an explicit alternative for the adjacent case ("For your own audio file use tempolor_split_stems") and tells the agent what to do when the call fails: a still-generating track answers 400 with status, and a 404 right after COMPLETED means retry in a few seconds. The guidance covers both when to use it and what to do when it doesn't succeed.

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