Skip to main content
Glama

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

List music tracks

pixverse_list_music
Read-onlyIdempotent

One account's music tracks: audio_id, status, prompt, model and mp3 url, a page at a time; pass next_offset as offset for the next page while has_more. Speech clips are listed by pixverse_list_speech, music videos by pixverse_list_music_videos. GET /music.

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

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 50).
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.4/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 safety bar is low; the description still adds real behavior: per-account scoping, pagination contract, and the underlying GET /music call. It does not state ordering or how empty results appear, which keeps it from 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?

Three compact clauses with the field list front-loaded and the routing sentence immediately after; nothing is padding. It is dense to the point of terseness in places ('while has_more'), which slightly hurts scanability.

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, and the description compensates by naming the returned fields and the pagination loop; the account parameter is fully specified in the schema. For a read-only paginated lister, an agent has everything needed to call it 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: it links the output field next_offset to the offset input and pairs it with has_more as the stop condition. That is genuine operational semantics beyond the property 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?

States a specific verb+resource ('One account's music tracks') and enumerates the returned fields (audio_id, status, prompt, model, mp3 url), then explicitly distinguishes itself from pixverse_list_speech and pixverse_list_music_videos. An agent can identify the right tool 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?

Names the two alternative listers explicitly so confused agents get routed correctly, and gives pagination usage ('pass next_offset as offset ... while has_more'). It stops short of stating positive conditions like 'use when you need to browse existing generated music', but the sibling exclusions carry the main disambiguation load.

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