Skip to main content
Glama

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

List music videos

pixverse_list_music_videos
Read-onlyIdempotent

One account's music videos: video_id, status, name and the finished video, a page at a time; pass next_offset as offset for the next page while has_more. pixverse_get_music_video reads one with its extra files. GET /music-video.

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_music_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 20).
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 and open-world, so the safety profile is covered. The description adds real value beyond them: it discloses the shape of a page (video_id, status, name, finished video), the has_more/next_offset cursor contract, and the underlying endpoint. It does not discuss rate limits or multi-account failure behavior in detail.

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?

Two dense sentences and an endpoint tag, front-loaded with the resource and its fields before the pagination mechanics. The first sentence is run-on and packs field enumeration, scope and paging into one clause, but nothing is redundant.

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?

There is no output schema, so the description must carry return-value information — and it does, naming the returned fields and the pagination fields an agent needs to iterate. Combined with existing annotation coverage, an agent has everything required to call and page through this tool correctly.

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, but the description adds meaning the schema cannot: offset is not an arbitrary index but the next_offset returned by the prior page, and has_more (a response field, absent from any output schema) is the continuation condition. The 'one account's' phrasing also motivates the email parameter.

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?

States a specific verb and resource (lists one account's music videos) plus the fields returned, which lets an agent tell it apart from the single-item pixverse_get_music_video, named explicitly. It does not distinguish itself from the similarly named pixverse_list_music_video_library, so sibling separation is incomplete but the core purpose is unambiguous.

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 concrete operating guidance: page size, and the pagination loop of passing next_offset as offset while has_more is true. It also routes single-item lookups to pixverse_get_music_video. It stops short of stating exclusions or when another listing tool (e.g. the music video library) would be the better choice.

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