Skip to main content
Glama

Finalize a Seedance draft to 1080p

aimixer_complete_draft
DestructiveIdempotent

PAID ACTION in two steps: finalize a finished Seedance 2.5 Draft to a 1080p video without generating it from scratch. A draft is a cheap 480p preview; if the user likes it, it can be finalized within the provider's draft validity window after its creation (7 or 14 days). Step 1: call with the draft's request_id (the one aimixer_submit / aimixer_status returned for the draft; result_index picks one of several results) and no quote_confirmation. It returns the coin price, quote_confirmation, pricing_revision, expected_price, approval_handle and approval_url; nothing is debited yet. Step 2: after the user explicitly approves that exact cost on the AIMixer website (or the supported inline button), call again with the same arguments plus quote_confirmation, pricing_revision, expected_price and approval_handle. It deducts coins and starts the finalization, returning a request_id to follow with aimixer_status. The returned price is the quote; charged_coins is the actual wallet debit (0 for free admin). Repeating the call for the same draft result never charges twice. Other models and generations are not drafts.

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": {
      "request_id": "<request_id>"
    },
    "name": "aimixer_complete_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesrequest_id of the finished draft generation.
result_indexNo
output_formatNomp4
expected_priceNo
approval_handleNo
pricing_revisionNo
quote_confirmationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say destructiveHint=true, idempotentHint=true; the description adds what the annotations cannot: that this is a paid action, that Step 1 debits nothing, that Step 2 deducts coins only after explicit user approval on the website or inline button, that the returned price is a quote while charged_coins is the real debit (0 for free admin), and that repeating the call never double-charges.

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 'PAID ACTION' and structured as Step 1 / Step 2, which matches the actual call sequence. It is dense but nearly every clause carries load; only minor redundancy, such as restating the quote-vs-charged distinction after already describing pricing.

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 paid, destructive, two-call finalization tool it covers the pricing, approval, idempotency and follow-up (aimixer_status) story, and an output schema exists so return values need not be enumerated. Residual gaps are small: no guidance on output_format choice and no stated expiry for approval_handle or quote_confirmation before reuse.

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 description coverage is only 14%, so the description must carry the load: it explains request_id as the draft generation's id, result_index as selecting one of several results, and explains the Step-2 echo parameters (quote_confirmation, pricing_revision, expected_price, approval_handle) as the values returned in Step 1 passed back verbatim. The output_format enum (mp4/mov) is never mentioned, leaving one parameter undocumented in both places.

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 (finalize a finished Seedance 2.5 Draft to a 1080p video) and immediately defines what a draft is (a cheap 480p preview), which is the key concept separating this tool from aimixer_submit. It also closes with 'Other models and generations are not drafts,' explicitly fencing off sibling behavior.

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 a concrete when-to-use condition (the user likes the cheap 480p preview) plus a constraint (must be within the 7/14-day draft validity window), and specifies that no other model or generation qualifies. The two-step sequence with the human-approval gate is spelled out rather than implied.

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