Skip to main content
Glama

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

List music video songs, characters and styles

pixverse_list_music_video_library
Read-onlyIdempotent

PixVerse's built-in songs (audio_path), characters (image_path) and styles (image_path) for pixverse_create_music_video, each with its name and url; type picks one group. Use them when you have no song or photo of your own (else pixverse_upload_file). GET /music-video/library.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly this group.
emailNoThe PixVerse account email, as pixverse_list_accounts shows it. Required when more than one account is configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real context beyond them: what each library group contains (audio_path for songs, image_path for characters and styles), that entries carry name and url, and that type narrows to a single group. It doesn't discuss pagination or library size, which would have completed the picture.

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 plus a bare endpoint reference; the purpose and the usage condition are front-loaded with no filler. The phrasing is slightly telegraphic ('each with its name and url; type picks one group'), but nothing is wasted.

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?

For a two-parameter, optional-argument list tool with no output schema, the description covers purpose, when to use it, the sibling alternative, the shape of the returned items, and the endpoint. An agent has everything needed to decide and 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 both parameters are documented structurally. The description still adds meaning beyond the schema by explaining what the enum values actually are – songs yield audio_path, characters and styles yield image_path – which helps an agent pick the right group rather than guess.

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 uses a specific verb (list) plus a precisely scoped resource: PixVerse's built-in songs, characters and styles for pixverse_create_music_video. It also distinguishes the tool from pixverse_upload_file, so an agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact condition for use ('when you have no song or photo of your own') and names the alternative route ('else pixverse_upload_file'). Both the when and the when-instead are explicit, which is exactly what routing needs.

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