Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

manga_title_staff

List a manga's staff credits—authors, artists, assistants, translators, letterers—with roles, occupations, images, volume ranges, and pagination. Use anime staff endpoint for anime IDs.

Instructions

List a manga's staff credits. Returns the people credited on a manga -- author, artist, assistants, and per-language translation and lettering credits -- with each person's role, occupations and image, paginated. Manga roles carry detail anime credits do not: a long-running series records volume ranges per credit (e.g. "Story & Art (vols 1-41)", "Supervisor (vols 41- )"). An anime id here returns 404 -- use GET /anime/title/{id}/staff for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAniList manga id
pageNo1-based page number, default 1
per_pageNoResults per page, default 10, max 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and largely does: it discloses the returned fields (role, occupations, image), that results are paginated, the manga-specific volume-range formatting of credits, and the 404-on-anime-id behavior. It omits auth/permission requirements and any note on default/max page sizes, which the schema covers instead.

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-loaded with the core action, then builds detail in three further sentences. The volume-range example earns its space by showing a real output shape, but the description is slightly longer than strictly necessary for a 3-param read tool.

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?

With no output schema and no annotations, the description compensates well by describing return contents, credit granularity, pagination, and error behavior. Only minor gaps remain (auth needs, page-size defaults), which are low-stakes for a read-only listing.

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% (id, page, per_page all documented), so baseline is 3. The description adds genuine semantic value to the required 'id' param by clarifying it must be a manga id and that an anime id fails with 404, which the schema's bare 'AniList manga id' does not convey.

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+resource ('List a manga's staff credits') and immediately enumerates the credit types returned (author, artist, assistants, per-language translation/lettering). It explicitly separates itself from the anime sibling by naming the anime staff endpoint, so an agent can distinguish the two without opening a schema.

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?

Gives an explicit when-not condition: an anime id returns 404 and the agent should use GET /anime/title/{id}/staff instead. That is a concrete routing rule plus the failure mode, not just implied context.

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

Deploy Server

Other Tools