Skip to main content
Glama

AI Manga & Anime Generator - Mangii MCP

by ai.mangii

List own stories

manga.list_stories
Read-onlyIdempotent

List stories you own, newest first. Call this when you lost story_id after context compaction so you can resume with manga.continue_story. Optional limit is an integer from 1 to 50 (default 20).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax stories to return. Integer from 1 to 50. Default 20. Omit to use the default.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoMachine error code such as invalid_request, insufficient_credits, or quality_forbidden.
messageNoHuman-readable error. Never includes stack traces or internal paths.
storiesYesOwned active stories, newest updated_at first.
next_stepYesWhat to call next. Follow this instead of guessing.

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already cover the safe read-only, idempotent, non-destructive profile, so the description's added 'newest first' ordering and the semantic that it lists owned stories carry useful extra information. It adds behavioral ordering context beyond the annotations without repeating them.

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 short sentences, no filler. The core action and ordering are front-loaded, and the when-to-use note is compactly integrated, followed by the parameter guidance.

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?

The tool is simple, has a single optional parameter, rich annotations that establish behavior, and an output schema. The description contains enough context about when and how to call it, including the concrete recovery scenario, for an agent to proceed safely.

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 description coverage is 100%, and the description repeats the same limit details already provided in the schema. The description adds no new meaning beyond the input-schema, which is acceptable for a single, clearly documented optional parameter.

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 the action and scope precisely: 'List stories you own, newest first.' It also clarifies the resource boundary from related tools by mentioning recovery after losing story_id, so an agent can distinguish it from manga.continue_story and manga.list_panels without opening schemas.

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 explicitly tells the agent when to call it: 'Call this when you lost story_id after context compaction so you can resume with manga.continue_story.' This provides clear context and names the continuation tool, though it does not explicitly enumerate when-not-to-use siblings.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: story creation, continuation, regeneration, panel listing, story listing, style listing, credit lookup, credit purchase, and job polling. Even the credit-related tools are clearly separated by purchase versus query. There is no meaningful overlap that would confuse an agent.

Naming Consistency5/5

All tools consistently use the manga. prefix with snake_case verb_noun names like create_story, list_panels, and regenerate_panel. The pattern is uniform across the entire set, making the API predictable and easy to navigate.

Tool Count5/5

Nine tools is a well-scoped size for a manga generation server: three creation-oriented tools, three listing tools, two credit tools, and one async job helper. Each tool serves a clear, non-redundant role in the workflow.

Completeness4/5

The core manga creation lifecycle is well covered: create, continue, regenerate, list stories, and list panels, plus style discovery and credit management. The only notable gaps are destructive operations like deleting stories or panels and perhaps a story detail endpoint, but these are not essential to the primary generation workflow.

Resources