Skip to main content
Glama

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

Upscale an image

pixverse_upscale_image

Upscale a PixVerse image (image_id) or your own upload (image_path) with pixverse-upscale or topaz-gigapixel (default pixverse-upscale); quote: true answers the exact price in credits and creates nothing. Uses PixVerse credits (412 when the account has too few). Waits up to ~50 s, then returns the new image_id for pixverse_get_image. POST /images/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_image"
  }
}

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 image_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-gigapixel: 1080p, 1440p, 2160p (1440p is 2K).
image_idNoThe image_id of a PixVerse image, e.g. user:12345-pixverse:you@example.com-image:123456789 (it names the account).
image_pathNoOr your own image: a path from pixverse_upload_file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the operation consumes PixVerse credits, returns error 412 when credits are insufficient, waits up to about 50 seconds by default, and returns a new image_id for retrieval. It also clarifies that quote mode is free and creates nothing, which is important for a non-read-only operation.

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?

The description is compact and front-loaded: purpose first, then quote behavior, credit implications, wait behavior, and return value. Every clause contributes useful operational context, with no unnecessary repetition.

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, the description usefully explains that a real run returns a new image_id for pixverse_get_image and that quote mode returns a price. However, the wait=false case says it returns 'the id at once' without clarifying whether that is an image_id or a job id or how an agent should later retrieve the result, leaving a gap for the asynchronous path.

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?

The input schema has 100% description coverage, so the baseline is 3. The description mainly restates parameter behavior already documented in the schema, such as quote returning a price and wait controlling the delay, and adds little parameter-level meaning beyond those schema descriptions.

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?

The description states a specific verb and resource: upscaling a PixVerse image or uploaded image. It names the supported models and distinguishes the quote-only mode from actual creation, so an agent can identify the operation 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?

It clearly explains the two source options, the default model, and when to use quote mode to get a price without creating anything. It does not provide explicit when-not guidance or explain how to choose topaz-gigapixel instead of the default beyond naming the options.

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