Skip to main content
Glama

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

Get an image

pixverse_get_image
Read-onlyIdempotent

One image from pixverse_create_image, pixverse_upscale_image or pixverse_list_images: image_status_name (QUEUED, GENERATING, PROCESSING, COMPLETED, FAILED, MODERATED) and, once completed, image_url, size and cost_credits (0 for a Relax Mode image), with the image as an image block. wait: true waits up to ~50 s. GET /images/{image_id}.

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_id": "<image_id>"
    },
    "name": "pixverse_get_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish.
image_idYesThe image_id, e.g. user:12345-pixverse:you@example.com-image:123456789 (it names the account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral context beyond that: the status lifecycle values, that image_url/size/cost_credits only appear once COMPLETED, that Relax Mode images report cost_credits 0, and that wait blocks up to ~50 s. It stops short of saying what is returned if the wait times out or the job is MODERATED/FAILED.

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?

A single dense sentence front-loads what is returned, then the sibling sources, then wait behavior and the endpoint. Every clause carries information, but packing status values, output fields and the Relax Mode edge case into one sentence makes it harder to scan than a short bulleted structure would be.

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 takes on the burden of describing returns and does so: status names, the completed-only fields, cost semantics and the image block. Combined with annotations covering safety and the fully documented two-parameter schema, an agent has everything needed to call and interpret this tool.

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 both parameters (image_id with a format example, wait with its meaning) are already documented in the schema. The description restates the ~50 s wait semantics and notes that image_id names the account, but adds no new syntax or constraints. Baseline 3 applies when the schema carries the parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this retrieves a single image's record (status plus, once done, image_url, size and cost_credits) for a given image_id, and it names the sibling tools that produce that id (create_image, upscale_image, list_images), plus the backing endpoint GET /images/{image_id}. That distinguishes it from the list and creation siblings. It is slightly indirect in phrasing ('One image from ...') rather than opening with an explicit verb, which keeps it just short of a 5.

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?

Guidance is clear by implication: this is the follow-up call you make on an image_id returned by pixverse_create_image, pixverse_upscale_image or pixverse_list_images, and wait: true polls for ~50 s instead of returning immediately. It does not explicitly say when not to use it (e.g., to enumerate many images use pixverse_list_images), so the exclusion is left to inference.

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