Skip to main content
Glama

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

Get a video

pixverse_get_video
Read-onlyIdempotent

One video by video_id, from any create, extend, modify, lip-sync or upscale tool: video_status_name (QUEUED, GENERATING, COMPLETED, FAILED, MODERATED) and, once completed, url, size, duration, model and, for a Seedance 2.5 draft, seedance_draft (can_create_final, expires_at). PixVerse answers 404 while a video is still processing; wait: true waits up to ~50 s through that. GET /videos/{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_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish.
video_idYesThe video_id, 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.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the full status vocabulary (QUEUED, GENERATING, COMPLETED, FAILED, MODERATED), the fact that the API answers 404 during processing, and that wait: true blocks up to ~50 s to bridge that. That is exactly the operational context an agent cannot get from structured fields.

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 resource and return shape, followed by the 404/wait caveat and finally the HTTP route. Dense and efficient, though the single long colon-chained sentence is harder to scan than it needs to be.

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?

With no output schema, the description carries the return burden and does so fully: status name, url, size, duration, model, and the Seedance 2.5 draft sub-fields (can_create_final, expires_at). Combined with the 404/wait behavior, an agent has everything needed to call and interpret the result.

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 meaning beyond the schema: it explains why wait exists (to ride out the 404 window) rather than merely restating its duration. The video_id format detail is largely duplicated from the schema, which keeps it out of 5 territory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: fetch one video by video_id, and enumerates the source tools whose jobs it can report on (create, extend, modify, lip-sync, upscale). It does not explicitly contrast itself with the nearest siblings such as pixverse_get_music_video or pixverse_get_image, but the resource is unambiguous enough that an agent can distinguish them.

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?

Clearly frames this as the polling/status-check tool following any of the video-producing tools, and gives a concrete condition for the wait flag (PixVerse returns 404 while processing). It lacks explicit when-not guidance or a named alternative for the multi-video case (e.g. a list tool), so it falls short of a 5.

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