Skip to main content
Glama

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

Upload an image, video or audio

pixverse_upload_file

Upload your own image (PNG, JPEG, GIF, WebP; PixVerse does not support images above about 2048 px), video (MP4, MOV, WebM and more) or audio (WAV, MP3) for use as a reference, up to 50 MB here (larger files: POST /files directly). Send a public https url or contentBase64 (small files). Returns the file's path (and an image's id): pass the path as image_path, first_frame_path, video_path or audio_path of the create tools; it works on any of your accounts. There is no delete for uploads. POST /files.

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

Input Schema

NameRequiredDescriptionDefault
urlNoA public https URL of the file.
emailNoThe PixVerse account email, as pixverse_list_accounts shows it. Required when more than one account is configured.
mimeTypeNoThe file's type. Default: from the url's answer.
contentBase64NoThe file content, base64-encoded (instead of url).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only cover the generic safety profile (readOnly=false, destructive=false, openWorld=true, idempotent=false); the description adds the real behavioral facts an agent needs: a ~50 MB and ~2048 px ceiling, that uploads are permanent because 'There is no delete for uploads', that the returned path works across any account, and that email is required when multiple accounts exist. That is substantially more than the annotations supply.

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?

The most decision-relevant facts (formats, size limits) are front-loaded and almost every clause carries new information. It is, however, a single dense run-on paragraph with stacked parentheticals and a stray trailing 'POST /files.' that restates the earlier escalation path, which costs it a point.

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 4-parameter, no-output-schema tool with an all-optional schema, the description covers limits, input-mode tradeoffs, return value ('the file's path (and an image's id)') and persistence. It could be more explicit about what happens if both url and contentBase64 are omitted or supplied together, but overall nothing essential is missing.

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 the baseline is 3; the description adds meaning on top by framing url as requiring a public https address and contentBase64 as the route for small files, which tells the agent how to choose between the two mutually exclusive inputs. It adds only marginal detail (the email precondition is already in the schema text), so it stops short of a 5.

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 opens with a specific verb and resource plus the accepted formats ('Upload your own image (PNG, JPEG, GIF, WebP)... video... or audio'), and it distinguishes itself from the create tools by naming the exact parameters (image_path, first_frame_path, video_path, audio_path) that consume its result. An agent can tell it apart from pixverse_create_image or pixverse_get_image 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?

It states the intended use case ('for use as a reference') and gives an explicit escalation path for oversized inputs ('larger files: POST /files directly'), and it says to use url for public files vs contentBase64 for small ones. What it does not do is contrast itself with the many sibling create/upload-adjacent tools, so the guidance is strong on conditions but thin on sibling alternatives.

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