Skip to main content
Glama

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

Multi-frame transition video

pixverse_create_transition

Generate one video through 2-7 keyframes in order, each move with its own prompt and duration, with v5, v5.5, v5.6 (3 or more frames: v5 only). For two frames on newer or third-party models use pixverse_create_video_frames. Uses PixVerse credits. Waits up to ~50 s, then returns the video_id for pixverse_get_video. POST /videos/create-transition.

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": {
      "frames": "<frames>"
    },
    "name": "pixverse_create_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoSeed for a repeatable result (native PixVerse models only).
waitNoWait up to ~50 s for the job to finish (default true); false returns the id at once.
audioNo2 frames on v5.5 / v5.6 only: true adds generated sound.
emailNoThe PixVerse account email (pixverse_list_accounts). Optional: by default a random account with a free slot.
modelNoDefault v5.6 for 2 frames, v5 for 3 or more.
framesYesThe keyframes in order. prompt and duration describe the move from this frame to the next (ignored on the last).
maxJobsNoOverride the account's maxJobs (jobs at once) for this request, 1-8.
qualityNoVideo quality.
preview_modeNotrue makes a fast lower-quality preview at 20% off credits (native PixVerse models only, paid plans).
off_peak_modeNotrue runs it in Off-Peak mode at a lower credit cost (native PixVerse models; the discount depends on the plan). Such a job is not waited for: read it later with pixverse_get_video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, openWorld=true, non-idempotent), the description discloses that credits are consumed, that the call blocks for ~50 s by default, that the result is a video_id to be read with pixverse_get_video, and that off-peak jobs are never waited for. That last caveat is a genuine behavioral trap the 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.

Conciseness4/5

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

Front-loaded with the core operation, then the sibling routing, then credits/wait/return, closing with the endpoint. Dense but every clause carries information; the endpoint path is the only borderline element for an agent's decision-making.

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?

For a 10-parameter asynchronous generation tool with no output schema, the description covers what is produced (a video_id), how to retrieve it, how long it blocks, and what happens in the non-waiting path. Nothing an agent needs to call this correctly and handle the result 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 coverage is already 100%, so the schema carries the parameter detail, but the description adds cross-parameter meaning the schema cannot: the model default flips between v5.6 and v5 depending on frame count, and off-peak mode changes whether the job is waited for. Minor gap: the frames array semantics (prompt/duration ignored on the last frame) live only 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 ("Generate one video through 2-7 keyframes in order") with the distinguishing mechanic spelled out: each move carries its own prompt and duration. It also names the sibling it is not for (pixverse_create_video_frames) and the models supported, so an agent can separate it from the other video-creation tools without opening a 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?

Gives explicit routing: 2-7 frames here, but two frames on newer or third-party models should use pixverse_create_video_frames. It also states the model constraint (3+ frames requires v5), the credit cost, and the wait behavior, which is exactly the when/when-not information an agent needs before calling.

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