Skip to main content
Glama

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

List tracks

tempolor_list_music
Read-onlyIdempotent

List one TemPolor account's songs or instrumentals (type), tracks made in the TemPolor web app included: job_id, titleEn, status, status_name, status_final, progress, cover, createTime, style, key, bpm, dur, model and the first 200 characters of the prompt. Pages: pass the cursor of the answer while hasNext is true. tempolor_get_music gives one track's full record and its mp3 url; tempolor_list_running_jobs only what this API tracks now. GET /music.

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_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNosong (default) or instrumental.song
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.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 and open-world, so the safety profile is covered. The description adds real behavior beyond them: the exact returned field set and the fact that prompt is truncated to its first 200 characters, which prevents an agent from treating this as a full-data source. It does not cover rate limits or invalid-cursor behavior, keeping it below a 5.

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: the listing action comes first, then the returned fields, then pagination, then the alternatives. The field enumeration is long and slightly awkward in its phrasing ('tracks made in the TemPolor web app included:'), but every clause carries information an agent needs.

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 correctly compensates by naming the returned fields and the prompt truncation, and it covers pagination and sibling routing. It is essentially complete for a read-only list tool; only edge conditions (invalid cursor, missing account) are unaddressed.

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 value beyond it by explaining the cursor continuation rule (hasNext-driven loop) and the song/instrumental type choice. The account-scoping nuance for user_id is left to the schema description.

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?

The description opens with a specific verb and resource ('List one TemPolor account's songs or instrumentals') and immediately clarifies the scope includes tracks created in the web app, then enumerates the returned fields. An agent can distinguish it from tempolor_get_music (single record) and tempolor_list_running_jobs (in-flight jobs only) without inspecting 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?

It explicitly routes the agent: use this for listing, use tempolor_get_music for one track's full record and mp3 url, use tempolor_list_running_jobs for what the API is tracking now. It also states the pagination loop condition ('pass the cursor of the answer while hasNext is true'), so the calling pattern is fully prescribed.

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