MeiGen AI Image Generation MCP

Overview Schema Source Related Servers Discussions Admin

render_video_draft

DestructiveIdempotent

Instructions

Render an owned completed draft as a separate paid 1080p final. Show the draft, quote check_generation seedanceDraft.finalCredits and obtain authorization first. This is the full final cost, not a price difference. Drafts expire at expiresAt. Reuse the same requestId/inputs on interruption. Only an explicitly authorized replacement after failure supplies retryFailedGenerationId and a new requestId. No changed prompt/references.

Input Schema

Name	Required	Description	Default
`requestId`	Yes
`confirmedCredits`	Yes
`retryFailedGenerationId`	No
`sourceDraftGenerationId`	Yes

Output Schema

Name	Required	Description	Default
`urls`	Yes
`error`	No
`status`	Yes
`deduped`	No
`modelId`	No
`success`	Yes
`imageUrl`	No
`provider`	No
`videoUrl`	No
`mediaType`	No
`requestId`	No
`savedPath`	No
`nextAction`	No
`creditsUsed`	No
`generationId`	No
`creditsStatus`	No
`failureDetail`	No
`seedanceDraft`	No
`receiptWarning`	No
`downloadWarning`	No
`observationEnded`	No
`pollAfterSeconds`	No
`requestedMediaType`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.3.0Oct 21, 2026

addedOutput schema / properties / failureDetail

Added value: +{
+  "enum": [
+    "video_edit_duration",
+    "reference_video_frame_rate"
+  ],
+  "type": "string"
+}

Addedv3.2.0Oct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond annotations (destructiveHint=true, idempotentHint=true): explains that this is the full final cost, not a price difference; that drafts expire at expiresAt; that the same requestId/inputs should be reused on interruption; and that retryFailedGenerationId is permitted only for an explicitly authorized replacement after failure.

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-loads the core action in sentence one, then layers the authorization and idempotency rules. Dense and telegraphic, but nearly every clause carries operational meaning; slightly abbreviated phrasing ('No changed prompt/references') costs a little readability.

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 destructive, cost-incurring mutation with an output schema present, the description covers preconditions, cost semantics, expiry, retry rules, and idempotency. Nothing an agent needs to call it safely is missing.

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?

With 0% schema description coverage, the description compensates well: it defines confirmedCredits as the full final cost sourced from check_generation, dictates requestId reuse vs. new requestId on retry, and restricts retryFailedGenerationId to authorized failure replacements. sourceDraftGenerationId is only implicitly described ('owned completed draft'), which prevents a full 5.

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 an owned completed draft as a separate paid 1080p final.' This clearly distinguishes it from generate_video (creates new) and check_generation (read-only status check).

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?

Explicit preconditions and procedure: show the draft, quote check_generation seedanceDraft.finalCredits, obtain authorization first. It also constrains usage ('owned completed draft', 'no changed prompt/references') and routes idempotency behavior. The alternative/sibling check_generation is named directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server