Skip to main content
Glama

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

Render a Seedance 2.5 draft in full quality

pixverse_create_final_video

Render a finished seedance-2.5-draft video again with Seedance 2.5 at 1080p or 2160p (4K), on the draft's account, while the draft is valid (its seedance_draft.can_create_final and expires_at in pixverse_get_video; drafts are kept 14 days). Only drafts; other videos: pixverse_upscale_video. Uses PixVerse credits by second and quality (see the pricing page). Waits up to ~50 s, then returns the new video_id for pixverse_get_video. POST /videos/create-final.

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": {
      "video_id": "<video_id>"
    },
    "name": "pixverse_create_final_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish (default true); false returns the id at once.
maxJobsNoOverride the account's maxJobs (jobs at once) for this request, 1-8.
qualityNo1080p (default) or 2160p (4K).
video_idYesThe video_id of a completed seedance-2.5-draft video, e.g. user:12345-pixverse:you@example.com-video:123456789 (it names the account).
relax_modeNoLeft out (or true), the plan's discount for Seedance 2.5 applies; false pays the full price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the safety bar is partly covered. The description still adds real value beyond them: credit consumption billed by second and quality, a ~50 s wait ceiling, and the returned video_id for follow-up. It does not say what happens to the source draft or whether a failed render still charges credits, which is the main remaining gap for a paid mutation.

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 action and resolution options, then preconditions, then the alternative, then cost and latency. Dense but every clause carries information; the nested parentheticals around can_create_final/expires_at make it slightly harder to scan than it needs to be.

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?

No output schema exists, yet the description states the return value (new video_id for pixverse_get_video) and the async behavior (waits ~50 s, or returns immediately with wait=false). Combined with preconditions, cost model, and the sibling routing, 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all five parameters are already documented, and the description largely restates quality tiers and the wait behavior. The one genuine addition is the cost framing around quality and the relax_mode discount ('Uses PixVerse credits by second and quality'), but it points to an external pricing page rather than explaining the tradeoff. Baseline 3 is appropriate when the schema carries the parameter burden.

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 and resource ('Render a finished seedance-2.5-draft video again with Seedance 2.5 at 1080p or 2160p') and pins the scope to drafts on the draft's own account. It explicitly names the sibling to use for non-draft videos (pixverse_upscale_video), so an agent can separate the two 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?

Gives an explicit when-not ('Only drafts; other videos: pixverse_upscale_video') plus the preconditions that gate the call: seedance_draft.can_create_final and expires_at from pixverse_get_video, with the 14-day retention window. That is when-to-use, when-not, and the alternative in one pass.

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