Skip to main content
Glama

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

Get a music track

pixverse_get_music
Read-onlyIdempotent

One track from pixverse_create_music or pixverse_list_music: audio_status_name (QUEUED, GENERATING, COMPLETED, FAILED) and, once completed, the mp3 url, duration and model; fail_reason when it failed. wait: true waits up to ~50 s. Speech clips are read with pixverse_get_speech. GET /music/{audio_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": {
      "audio_id": "<audio_id>"
    },
    "name": "pixverse_get_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish.
audio_idYesThe audio_id of a music track, e.g. user:12345-pixverse:you@example.com-music:123456789 (it names the account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the actual response contract — audio_status_name with its four states, mp3 url, duration and model once COMPLETED, and fail_reason on failure — plus the polling semantic that wait: true blocks up to roughly 50 s. That is exactly the lifecycle and timing context annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense paragraph, front-loaded with the resource identity, then return fields, then the wait flag, then the sibling redirect. Every clause carries distinct load; even the trailing endpoint path is a compact mental anchor rather than filler.

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?

There is no output schema, so the description takes on the return-value burden and does so: field names, status enumeration, completion payload and failure field are all covered, alongside the blocking behaviour of wait. Nothing an agent needs in order to call and interpret this tool 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 description coverage is 100%, so the baseline is 3; the description earns above that by adding provenance for audio_id (it comes from create_music or list_music) and by tying wait to an approximate 50 s ceiling. It does not add anything about the audio_id format beyond the schema's own example, so it stays short of a 5.

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 concrete verb+resource — 'One track' retrieved by audio_id — and immediately disambiguates from sibling resources by naming the two tools that produce the id (pixverse_create_music, pixverse_list_music) and by routing speech clips to pixverse_get_speech. An agent can distinguish this from pixverse_get_music_video or pixverse_list_music without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It states where the required audio_id comes from (create_music or list_music) and explicitly redirects the speech case to pixverse_get_speech, which is a real alternative-selection rule. It stops short of spelling out when to prefer this over a bulk listing or after which step in a pipeline to poll, so it is strong but not exhaustive.

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