Skip to main content
Glama

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

Make a music video

pixverse_create_music_video

Make a full music video from a song (audio_path: an uploaded MP3, 10 seconds to 6 minutes, or a library song) and optionally a character photo: performance (default), expressive or storytelling mode, a style, lyric captions, 720p or 1080p. Credits per second of song by mode and quality; the first music video of every account is free; quote: true answers the exact price and creates nothing. Waits up to ~50 s, then returns the video_id for pixverse_get_music_video. POST /music-video/create.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "audio_path": "<audio_path>"
    },
    "name": "pixverse_create_music_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoDefault performance.
waitNoWait up to ~50 s for the job to finish (default true); false returns the id at once.
emailNoThe PixVerse account email (pixverse_list_accounts). Optional: by default a random account with a free slot.
quoteNotrue returns the price and creates nothing (free).
styleNoThe look. performance / expressive: auto, custom, cinematic, underground, decadence, holiday, candy, woolen_felt, lo_fi, futuristic, chromatic_clash, golden_age, woodland_tale, dreamscape, voxel, retro_game, claymation, impressionism (default auto). storytelling: photorealistic, anime, 2d_modern_animation, cyberpunk, high_energy, digital_art, pixel_art, city_pop, y2k_collage, illustration, sketch, rock_haze, bubble_gum_punk, claymation, metal_noir, ghibli, midnight_blue_soul, lego_blocks (default photorealistic).
lyricsNoWith subtitles: true, the lyrics one line per caption.
promptNostorytelling only, and required there: the story to tell.
maxJobsNoOverride the account's maxJobs (jobs at once) for this request, 1-8.
qualityNoDefault 720p.
subtitlesNotrue burns lyric captions into the video (a copy without them comes too); not with storytelling.
audio_pathYesThe song: a path from pixverse_upload_file (MP3) or a songs[].audio_path from pixverse_list_music_video_library.
image_pathNoThe performer: an uploaded photo or a library character; without it PixVerse invents one.
music_genreNoHelps PixVerse read the song; not with storytelling.
aspect_ratioNoDefault 16:9.
image_path_2Nostorytelling only: a second character (needs image_path).
style_image_pathNoWith style custom only: an image whose look the video copies (upload or library style).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare the generic write/open-world profile; the description adds real behavior: credit cost scales per second by mode and quality, the first video is free, quote:true is a dry run that creates nothing, and the call blocks ~50 s before returning an id. That is exactly the cost and side-effect context an agent needs before committing to a paid job.

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?

Front-loaded with the purpose, then inputs, then cost, then return flow — a sensible ordering. The parenthetical enumerations are dense and a few lists (style, mode) read as compressed shorthand, but no sentence is filler.

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 16-parameter paid generation tool with no output schema, the description still supplies the return value (video_id), the wait semantics, the quoting path, and the cost model. The remaining uncovered surface is minor because every parameter carries a schema description.

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 goes beyond it by constraining audio_path (MP3, 10 seconds to 6 minutes, or a library song), noting the optional character photo, and listing the mode/style/resolution axes. Many other parameters (email, maxJobs, aspect_ratio, music_genre, style_image_path) are left entirely to the schema.

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?

Opens with a specific verb and resource ('Make a full music video from a song') and scopes the inputs (audio_path, optional character photo, modes, style, resolution). It clearly distinguishes itself from pixverse_get_music_video by naming it as the follow-up step, though it does not differentiate against other creation siblings like pixverse_create_video or pixverse_create_final_video.

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 actionable routing: 'quote: true answers the exact price and creates nothing', 'Waits up to ~50 s, then returns the video_id for pixverse_get_music_video'. Also states default mode is performance and that the first music video per account is free. No explicit when-not-to-use guidance versus other video-creation tools, which keeps it below 5.

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