AI Manga & Anime Generator - Mangii MCP

Regenerate manga panel

manga.regenerate_panel

Redraw or edit one panel. Style stays locked. Same Image 1 / Image 2 ref overrides as manga.continue_story. Get ids from manga.list_panels. Costs the same credits as a new panel.

Input Schema

TableJSON Schema

Name	Required	Description
`async`	No	On this MCP server the default is false: wait and return image_url in one call. Set true only if you will poll manga.get_job. HTTP API default remains async.
`prompt`	No	Optional rewrite of the scene. Same prompt rules as create. Omit to retry the stored prompt.
`quality`	No	Generation quality. standard costs 1 credit, hd 2, ultra 5. Default standard. HD/Ultra need an unlocked API wallet.
`panel_id`	Yes	Panel id from a previous generate result or manga.list_panels. Example: the panel_id returned by manga.create_story.
`story_id`	Yes	Story id from manga.create_story. Example: a Firestore story document id returned as story_id.
`identity_image`	No	Replacement photo: https URL or data:image/...;base64,... URI. Public hosts only. Same slot cannot also send a panel id.
`idempotency_key`	No	Optional. Reuse the same key on retry so a timeout does not charge twice. 8-200 chars. Omit to mint a one-shot key (unsafe on retry).
`reference_image`	No	Alias for identity_image. Replaces Image 1 with an uploaded photo or URL.
`continuity_image`	No	Replacement Image 2 (scene) photo: https URL or data URI. Do not also send continuity_panel_id.
`context_panel_ids`	No	Legacy list override [identity_panel_id, scene_panel_id]. Ignored when identity_* or continuity_* fields are set. Prefer those named slots.
`identity_panel_id`	No	Override Image 1 (identity) with this panel id from manga.list_panels. Do not also send identity_image.
`continuity_panel_id`	No	Override Image 2 (scene) with this panel id from manga.list_panels. Do not also send continuity_image.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Machine error code such as invalid_request, insufficient_credits, or quality_forbidden.
`job_id`	No	Async job id when async is true or the work is still running.
`message`	No	Human-readable error. Never includes stack traces or internal paths.
`quality`	No	Quality used for this generation.
`panel_id`	No	Generated or regenerated panel id.
`story_id`	No	Created or existing story id.
`image_url`	No	HTTPS URL of the finished panel when async is false and generation succeeded.
`next_step`	No	What the agent should call next. Follow this instead of guessing.
`request_id`	No	Request correlation id.
`credits_charged`	No	API credits billed for a successful generation.
`credits_remaining`	No	Remaining spendableCredits after the call (apiPack plus packCredits after a purchase).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

changedOutput schema / properties / credits_remaining / description

Previous value: -"Remaining spendableCredits after the call (apiPack plus purchase-backed packs)."New value: +"Remaining spendableCredits after the call (apiPack plus packCredits after a purchase)."

Changed2 schema fields changedAug 23, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Optional. Reuse the same key on retry so a timeout does not charge twice. 8-200 chars. Omit to mint a one-shot key (unsafe on retry).",
+  "maxLength": 200,
+  "minLength": 8,
+  "type": "string"
+}

changedOutput schema / properties / credits_remaining / description

Previous value: -"Remaining apiPackCredits after the call."New value: +"Remaining spendableCredits after the call (apiPack plus purchase-backed packs)."

Changed7 schema fields changedAug 23, 2026

addedInput schema / properties / context_panel_ids

Added value: +{
+  "description": "Legacy list override [identity_panel_id, scene_panel_id]. Ignored when identity_* or continuity_* fields are set. Prefer those named slots.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / continuity_image

Added value: +{
+  "description": "Replacement Image 2 (scene) photo: https URL or data URI. Do not also send continuity_panel_id.",
+  "type": "string"
+}

addedInput schema / properties / continuity_panel_id

Added value: +{
+  "description": "Override Image 2 (scene) with this panel id from manga.list_panels. Do not also send continuity_image.",
+  "type": "string"
+}

addedInput schema / properties / identity_image

Added value: +{
+  "description": "Replacement photo: https URL or data:image/...;base64,... URI. Public hosts only. Same slot cannot also send a panel id.",
+  "type": "string"
+}

addedInput schema / properties / identity_panel_id

Added value: +{
+  "description": "Override Image 1 (identity) with this panel id from manga.list_panels. Do not also send identity_image.",
+  "type": "string"
+}

changedInput schema / properties / panel_id / description

Previous value: -"Panel id from a previous generate result. Example: the panel_id returned by manga.create_story."New value: +"Panel id from a previous generate result or manga.list_panels. Example: the panel_id returned by manga.create_story."

addedInput schema / properties / reference_image

Added value: +{
+  "description": "Alias for identity_image. Replaces Image 1 with an uploaded photo or URL.",
+  "type": "string"
+}

AddedAug 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, so the agent knows it's a write operation. The description adds behavioral context: 'Style stays locked' and the credit cost, plus the image override semantics via continue_story. It does not explicitly state whether the panel is overwritten or a new version is created, but given the annotations cover mutation, this is acceptable.

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?

Two sentences with no filler: purpose first, then key constraints (style lock, image refs), then practical guidance (where to get IDs) and cost. Every sentence adds value and the structure is front-loaded with the main action.

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?

An output schema exists, so return values are covered. The description provides the critical operational details: style lock, image override behavior, ID source, and cost. It does not mention async behavior or idempotency, but those are in the schema. For a 12-parameter tool with a rich schema, this description is sufficiently complete.

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 description does not need to explain parameters. It adds a hint about image overrides (Image 1 / Image 2) which relates to parameters like identity_image and continuity_image, but this is not necessary since the schema already documents all fields with descriptions. Baseline 3 is appropriate.

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?

The description states a specific action ('Redraw or edit one panel') with a clear resource, and distinguishes it from sibling tools by mentioning 'Style stays locked' and 'Same Image 1 / Image 2 ref overrides as manga.continue_story', which signals it is for panel-level regeneration rather than story continuation. The verb is clear and not a tautology.

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?

It tells the agent where to get IDs ('Get ids from manga.list_panels') and notes that the image override behavior matches manga.continue_story, giving practical context. It does not explicitly contrast with all siblings, but it implies that for new panels one would use create_story and for continuation continue_story. It also mentions cost, which is useful for deciding when to use it.

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

All AI Manga & Anime Generator - Mangii MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.