Skip to main content
Glama

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

Extend a video

pixverse_extend_video

Continue a video from its last frame with v6 or grok-imagine: a PixVerse video (video_id, on its account) or your own upload (video_path). To change what is in a video use pixverse_modify_video. Uses PixVerse credits. Waits up to ~50 s, then returns the new video_id for pixverse_get_video. POST /videos/extend.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pixverse_extend_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoSeed (v6 only).
waitNoWait up to ~50 s for the job to finish (default true); false returns the id at once.
audioNov6 only: true adds generated sound to the new part.
emailNoThe account email, used only with video_path.
modelNoThe extending model.
promptNoWhat happens next.
maxJobsNoOverride the account's maxJobs (jobs at once) for this request, 1-8.
qualityNoVideo quality, by model.
durationNoSeconds to add, by model.
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.6/5.0
Behavior4/5

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

Annotations only declare mutation/open-world/no-idempotency; the description adds real context beyond them: credit consumption, a ~50 s bounded wait, async off-peak jobs needing pixverse_get_video, and what is returned. It stops short of saying what happens if the wait times out, but the async contract is otherwise well disclosed.

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?

Two tightly packed sentences plus the endpoint, front-loaded with the core action and the source choice. Every clause carries information (model choice, alternative tool, cost, wait, return path); nothing is filler.

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 12-parameter, no-output-schema mutation tool it covers the essentials: inputs, cost, timing, async handling, and what id comes back. Only the timeout/partial-failure edge case is left implicit.

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 baseline is 3; the description still adds the meaningful selection logic between the two input paths (video_id's embedded account vs email+video_path) and reinforces model-scoped limits like v6-only seed/audio. That is value beyond the parameter blurbs.

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?

Specific verb and resource: 'Continue a video from its last frame', scoped to two models and two input sources (video_id on its account vs video_path upload). It also explicitly contrasts with pixverse_modify_video, so an agent can distinguish it from siblings without opening schemas.

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 an explicit alternative and the condition that selects it ('To change what is is in a video use pixverse_modify_video'), notes the credit cost, and states the follow-up path (new video_id for pixverse_get_video). Off-peak behavior is also flagged as not waited for.

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