Skip to main content
Glama

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

Modify a video by prompt

pixverse_modify_video

Change what is in an existing video by a prompt, with v5.5, at 360p, 540p, 720p: a PixVerse video (video_id) or your own upload (video_path). To lengthen a video use pixverse_extend_video. Uses PixVerse credits by the video's length and quality. Waits up to ~50 s, then returns the new video_id for pixverse_get_video. POST /videos/modify.

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": {
      "prompt": "<prompt>"
    },
    "name": "pixverse_modify_video"
  }
}

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.
emailNoThe account email, used only with video_path.
modelNoDefault v5.5.
promptYesThe change to make.
maxJobsNoOverride the account's maxJobs (jobs at once) for this request, 1-8.
qualityNoVideo quality (no 1080p).
video_idNoThe video_id of a PixVerse video (pixverse_list_videos, a create tool); its account is used, e.g. user:12345-pixverse:you@example.com-video:123456789 (it names the account).
video_pathNoOr your own 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.1/5.0
Behavior4/5

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

Annotations already flag it as a non-read-only, non-idempotent, open-world mutation, so the description need not restate safety. It adds genuinely useful behavior: credit consumption scaled by video length and quality, a ~50 s wait ceiling, the returned video_id, and the caveat that off-peak jobs are not waited on.

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 action and scope, then alternatives, cost, and latency in quick order; no filler sentences. Minor redundancy in repeating the 360p/540p/720p and v5.5 enum values that already live in the schema.

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 10-parameter async generation tool with no output schema, it covers the essentials an agent needs: source choice, cost, wait semantics, async fallback, and how to retrieve the result. Missing only edge guidance such as failure/refund behavior or what happens on timeout.

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 carries parameter meaning and baseline is 3. The description restates the quality enum and v5.5 model and clarifies the video_id/video_path fork, but adds little beyond what the field descriptions already say.

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 ('Change what is in an existing video by a prompt') and immediately scopes it to the two accepted sources (video_id or video_path). It explicitly separates itself from pixverse_extend_video, so an agent can distinguish modify-in-place from lengthening 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 Guidelines4/5

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

Gives clear when-to-use context: modify content here, use pixverse_extend_video to lengthen, and it names the follow-up pixverse_get_video. It does not address other plausible alternatives in the sibling catalog (e.g. upscale, lipsync, create_video) or when a fresh create is preferable to a modify.

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