Skip to main content
Glama

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

Upscale a video

pixverse_upscale_video

Upscale a PixVerse video (video_id) or your own MP4 / MOV upload (video_path, under 4K, up to 3 minutes) with pixverse-upscale, topaz-proteus, topaz-starlight-fast, topaz-starlight-precise (default pixverse-upscale); quote: true answers the exact price in credits and creates nothing. Credits per second of the video, by model and quality (412 when the account has too few). Waits up to ~50 s, then returns the new video_id for pixverse_get_video. POST /videos/upscale.

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_upscale_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 pixverse-upscale.
quoteNotrue returns the price and creates nothing (free).
maxJobsNoOverride the account's maxJobs (jobs at once) for this request, 1-8.
qualityNoDefault 2160p. pixverse-upscale: 2160p; topaz-proteus: 1080p, 2160p; topaz-starlight-fast: 1080p, 2160p; topaz-starlight-precise: 1080p, 2160p.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

This is a significant gap in the context of an 8-parameter mutation tool. Better: annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-redundant behavior: credit cost per second of video by model and quality, the 412 failure when the account has too few credits, a ~50 s wait then return of the new video_id, and upload limits (<4K, up to 3 minutes).

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?

Effectively front-loaded: the resource and the two input branches come first, then models/default, then the quote escape hatch, then cost and timing. Nearly every clause adds operative information, though the phrase "412 when the account has too few" is terse enough to be cryptic without the surrounding context.

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?

With no output schema and 8 parameters, the description covers the mutation's cost, its pause-then-return behavior, the returned id and its follow-up tool, and the input constraints. The remaining gap is that "credits per second ... by model and quality" never states any actual figures, so an agent cannot predict cost without calling quote:true.

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 coverage is 100%, so most parameter meaning is already in the schema, making 3 the baseline. The description contributes the non-schema constraints on video_path (under 4K, up to 3 minutes) and the fact that quote is free and creates nothing, but it repeats the model list and default verbatim from 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 (upscale a video) and immediately distinguishes the two input sources: a PixVerse video_id versus your own MP4/MOV via video_path. It also enumerates the four model choices and the default, so an agent can tell this apart from pixverse_upscale_image 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 Guidelines4/5

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

Gives clear usage context: quote:true answers a price and creates nothing, and a successful run returns a new video_id to hand to pixverse_get_video, which routes the follow-up step. No explicit when-not or comparison to sibling tools such as pixverse_upscale_image is offered, keeping it below a 5.

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