Skip to main content
Glama

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

List videos

pixverse_list_videos
Read-onlyIdempotent

One account's PixVerse videos, including those still queued or generating and music videos (made with the API or on pixverse.ai): video_id, status, prompt, model and url, a page at a time; pass next_offset as offset for the next page. pixverse_get_video reads one video. GET /videos.

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

Input Schema

NameRequiredDescriptionDefault
emailNoThe PixVerse account email, as pixverse_list_accounts shows it. Required when more than one account is configured.
limitNoItems per page (default 40).
offsetNoWhere the page starts (default 0): the next_offset of the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real behavior — that in-flight jobs appear in results and that results are paged with a next_offset cursor. It omits ordering guarantees and what happens with the email parameter when multiple accounts exist, which keeps it short of a 5.

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?

One dense sentence plus a short disambiguation clause and the endpoint — front-loaded with scope and return fields. The parenthetical about API vs pixverse.ai is slightly noisy but does convey coverage; no filler sentences.

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?

Without an output schema, the description compensates by listing the returned fields, and it documents cursor paging and the account-scoping nuance the schema handles. Ordering of results and the exact meaning of status values are the remaining gaps, but nothing essential to calling it correctly is missing.

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%, including the next_offset-to-offset chaining, so the schema carries most param meaning. The description only restates the paging idiom and adds no new semantics for limit or email beyond what the schema already documents; baseline 3 applies.

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 resource (one account's PixVerse videos) with explicit scope — includes queued/generating items and music videos — and enumerates the returned fields (video_id, status, prompt, model, url). It explicitly names the sibling pixverse_get_video as the single-item alternative, so an agent can distinguish them 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 operating context: paginated retrieval, use pixverse_get_video for one video, and pass the previous page's next_offset as offset. It does not address when to prefer it over the other list tools (notably pixverse_list_music_videos, which overlaps with the 'including music videos' claim), leaving that boundary ambiguous.

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