Skip to main content
Glama

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

Get a music video

pixverse_get_music_video
Read-onlyIdempotent

One music video from pixverse_create_music_video: status (pending, processing, succeeded, failed), its settings and, once succeeded, the video (url, cover_url, size, duration) and extra files such as the copy without captions. wait: true waits up to ~50 s. Delete it with pixverse_delete_video. GET /music-video/{video_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": {
      "video_id": "<video_id>"
    },
    "name": "pixverse_get_music_video"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With annotations already declaring readOnly/idempotent/non-destructive, the description adds real behavior: the job lifecycle states (pending, processing, succeeded, failed), what is only available after success, and the ~50 s ceiling on the wait flag. It also exposes the underlying endpoint, so an agent knows exactly what resource is read.

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?

The result payload is front-loaded in a single compact sentence, followed by the wait caveat and a delete pointer, with zero filler. The colon-separated enumeration is dense and slightly run-on, 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.

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 must carry the return contract, and it does: status, settings, and per-status availability of url/cover_url/size/duration plus caption-free copies. For a two-parameter read, nothing needed to call or interpret it 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 coverage is 100% and both parameters are documented there, so the schema does the heavy lifting and baseline 3 applies. The description restates the wait behavior and the status set but contributes no format or syntax detail beyond the schema's own text.

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+resource ('One music video from pixverse_create_music_video') and immediately enumerates the returned shape: status, settings, video fields, extra files. It ties the tool to the sibling that produces the job and separates itself from the delete path, so an agent can distinguish retrieve-from-create versus delete without opening the 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?

Gives concrete usage context: this is the follow-up to pixverse_create_music_video, with 'wait: true' for a ~50 s blocking poll, and routes removal to pixverse_delete_video. It stops short of explicitly contrasting polling versus listing via the library/list siblings, so no true when-not guidance exists.

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