Skip to main content
Glama

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

Animate a character with a motion video

pixverse_motion_control

Make the person or animal in a character image move like the subject of a reference video (PixVerse motion control, v5.6); no prompt. The image must show a clear subject (422 otherwise). Both are paths from pixverse_upload_file. Uses PixVerse credits by the motion video's length. Waits up to ~50 s, then returns the video_id for pixverse_get_video. POST /videos/motion-control.

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": {
      "image_path": "<image_path>",
      "video_path": "<video_path>"
    },
    "name": "pixverse_motion_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish (default true); false returns the id at once.
emailNoThe PixVerse account email (pixverse_list_accounts). Optional: by default a random account with a free slot.
modelNoDefault v5.6.
maxJobsNoOverride the account's maxJobs (jobs at once) for this request, 1-8.
qualityNoVideo quality.
image_pathYesThe character image: a path from pixverse_upload_file.
video_pathYesThe motion reference video: a path from pixverse_upload_file.
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.5/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; the description adds real behavior: credit consumption scaled to the motion video's length, the ~50 s blocking wait with video_id as the async fallback, and the 422 condition for subjectless images. That is substantive disclosure beyond the safety hints.

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?

Three compact sentences front-load the action, then prerequisites and cost/return behavior; every clause carries information (version, no prompt, 422 rule, upload source, credits, wait, follow-up tool, endpoint). Nothing is padding.

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 still explains what comes back (video_id) and how to retrieve the result; cost model, failure mode, and input provenance are all covered. An agent has everything needed to call it and handle the outcome.

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 description coverage is 100%, so the schema already documents wait, email, model, maxJobs, quality, off_peak_mode, and both paths. The description only reinforces that the two path parameters originate from pixverse_upload_file, which is useful but marginal; baseline 3 applies.

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?

Names a specific verb and resource ('Make the person or animal in a character image move like the subject of a reference video'), pins the PixVerse feature and version (motion control, v5.6), and disambiguates from prompt-based siblings with 'no prompt'. An agent can identify this as the image+motion-video animation tool 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 preconditions (image must show a clear subject or 422; both inputs are paths from pixverse_upload_file) and an explicit next step (video_id for pixverse_get_video). It does not explicitly state when to prefer this over pixverse_create_video or pixverse_modify_video, so alternatives are implied rather than spelled out.

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