AI Manga & Anime Generator - Mangii MCP

Continue manga story

manga.continue_story

Add the next panel. Do not send style_id. Defaults: Image 1 = first panel (identity), Image 2 = last distinct panel (scene). Override via manga.list_panels then identity_panel_id or identity_image and/or continuity_panel_id or continuity_image. Same credit costs as create.

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`	Yes	Scene in everyday language: characters, place, action, mood, camera, weather, color or black-and-white. Example: "A duel under cherry blossoms, low angle, rain, full color." Max 2000 characters.
`quality`	No	Generation quality. standard costs 1 credit, hd 2, ultra 5. Default standard. HD/Ultra need an unlocked API wallet.
`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)."

Changed6 schema fields changedAug 23, 2026

changedInput schema / properties / context_panel_ids / description

Previous value: -"Override default refs. Omit to use first panel as identity and, when the story has 2+ panels, the last panel as scene. Example: [\"identity_panel_id\",\"scene_panel_id\"]."New value: +"Legacy list override [identity_panel_id, scene_panel_id]. Ignored when identity_* or continuity_* fields are set. Prefer those named slots."

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"
+}

addedInput schema / properties / reference_image

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

Changed1 schema field changedAug 23, 2026

changedInput schema / properties / context_panel_ids / description

Previous value: -"Optional prior panel ids to use as continuity. Example: [\"panel_abc\"]. Omit to use server defaults."New value: +"Override default refs. Omit to use first panel as identity and, when the story has 2+ panels, the last panel as scene. Example: [\"identity_panel_id\",\"scene_panel_id\"]."

AddedAug 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations say readOnly=false and destructive=false, so this is a write operation. The description adds meaningful behavioral context: default panel identity/scene mapping, override semantics, and credit cost parity with create. It does not describe the return payload, but an output schema exists, so that burden is already covered.

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?

Four short sentences with no filler. The core action is front-loaded, and each sentence carries operational value: the default behavior, override workflow, and cost. It avoids repeating schema details.

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 an 11-parameter mutation tool with full schema coverage and an output schema, the description covers the non-obvious operational aspects: defaults, overrides, exclusions, and costs. Nothing critical is missing for an agent to invoke the tool correctly.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining the relationship between Image 1/Image 2 defaults and the identity/continuity override parameters, and by pointing to manga.list_panels for obtaining valid panel IDs. This helps agents understand how the parameters work together.

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 opens with 'Add the next panel', a specific verb and resource that clearly identifies the operation as extending an existing manga story. This differentiates it from siblings like manga.regenerate_panel (replacing an existing panel) and manga.create_story (starting a new story). The title 'Continue manga story' reinforces the purpose.

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?

The description gives explicit usage guidance: do not send style_id, the default image slot behavior, and how to override via manga.list_panels plus identity/continuity fields. It also clarifies credit costs relative to create. It does not explicitly contrast with regenerate_panel, but the guidance for overriding and defaults is concrete enough for correct invocation.

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.