MeiGen AI Design MCP

check_generation

Idempotent

Retrieve a MeiGen job without new charges by providing generationId or requestId, then follow its structured status and nextAction—useful after a lost submit response, restart, or host change.

Instructions

Read an existing MeiGen job without new charges. Provide generationId OR the caller requestId UUID. requestId lookup works after a lost submit response, process restart or another host. Follow structured status and nextAction; do not turn an uncertain status into a new paid UUID.

Input Schema

Name	Required	Description
`requestId`	No	Original workflow step UUID supplied to generate_image/video; authenticated lookup across hosts. Provide exactly one identifier.
`generationId`	No	Accepted generation ID. Provide exactly one of generationId and requestId.
`requestedMediaType`	No	Original workflow step intent, when known. Preserve it from nextAction.arguments to detect a completed result of the other media type; this does not change or resubmit the job.

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.

First observedv3.3.3Nov 1, 2026

TDQS

A3.5/5.0

Behavior1/5

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

The description explicitly frames the tool as a read operation ('Read an existing MeiGen job') with no new charges, while annotations declare readOnlyHint=false. This is a direct contradiction, and the description does not disclose any non-read-only side effect that would justify the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it states the read/no-charge behavior first, then identifier requirements, recovery scenarios, and status-handling guidance. Every sentence contributes actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the usage guidance is complete. However, the read-only contradiction leaves a material gap about whether the tool has side effects beyond avoiding new charges.

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 coverage is 100%, so the schema already documents all three parameters. The description adds useful recovery context for requestId lookup, but it does not add much beyond the schema for generationId or requestedMediaType.

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?

The description gives a specific verb and resource: it reads an existing MeiGen job without incurring new charges. It is clearly a status/check operation rather than a generation operation, though it does not explicitly name sibling tools for differentiation.

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 exactly which identifiers to provide and explains when requestId lookup is useful: after a lost submit response, process restart, or from another host. It also gives a clear caution not to turn an uncertain status into a new paid UUID.

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

Deploy Server