Skip to main content
Glama

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

Video from a first and last frame

pixverse_create_video_frames

Generate a video that moves from a first frame to a last frame (two uploaded images), with V5.6 (default), V5.5, V5, V6, C1 or third-party models (Seedance, Kling, Veo 3.1, MiniMax H3, Wan 3.0); the first frame sets the aspect ratio. For three to seven frames use pixverse_create_transition; for one image, pixverse_create_video. Uses PixVerse credits. Waits up to ~50 s, then returns the video_id for pixverse_get_video. POST /videos/create-frames.

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": {
      "first_frame_path": "<first_frame_path>",
      "last_frame_path": "<last_frame_path>"
    },
    "name": "pixverse_create_video_frames"
  }
}

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.
audioNotrue adds generated sound where the model has an audio toggle (see the model capabilities page).
emailNoThe PixVerse account email (pixverse_list_accounts). Optional: by default a random account with a free slot.
modelNoDefault v5.6.
promptNoWhat happens between the frames.
maxJobsNoOverride the account's maxJobs (jobs at once) for this request, 1-8.
qualityNoOptional on v5, v5.5 and v5.6; required on v6, pixverse-c1 and third-party models.
durationNoSeconds: 1-8 on v5, v5.5 and v5.6 (default 5); required on v6, pixverse-c1 and third-party models.
relax_modeNoThird-party models only (400 on PixVerse's own). Left out (or true), the plan's discount for the model applies; false pays the full price.
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.
last_frame_pathYesThe last frame: a path from pixverse_upload_file.
first_frame_pathYesThe first frame: a path from pixverse_upload_file.

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?

Annotations only declare write/open-world/non-idempotent, but the description adds the details that matter: consumption of PixVerse credits, a ~50 s blocking wait with a video_id可能 returned for later retrieval, and the fact that first frame determines aspect ratio. It even documents an exception to the wait behavior in the sibling parameter docs, which is the kind of nuance annotations cannot carry.

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 action, then sibling routing, then cost and async behavior, then the endpoint. The list of model families restates what the model enum already enumerates, adding length without new decision value.

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?

For a 14-parameter generation tool with no output schema, the description covers purpose, alternatives, cost, execution mode, and what is returned. Minor gaps remain around credit amounts, failure behavior, and image compatibility constraints, but nothing essential for correct invocation 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 100%, so the baseline is 3; the description earns extra credit by disclosing the model lineup and default (V5.6), the aspect-ratio rule tied to the first frame, and the wait/return semantics. The model enumeration partially duplicates the schema enum, which keeps it from 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?

States a specific verb and resource with the exact scope: a video that moves from a first frame to a last frame using two uploaded images. It goes further by naming the sibling to use for 3-7 frames (pixverse_create_transition) and for a single image (pixverse_create_video), so an agent can distinguish it 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 Guidelines5/5

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

Explicit routing rules: three to seven frames -> pixverse_create_transition, one image -> pixverse_create_video, and the returned video_id -> pixverse_get_video. It also flags the credit cost and the ~50 s wait so the agent knows the operational trade-off 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