Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

manga_title_characters

List a manga's characters by AniList manga ID, returning cast names, native names, billed roles, images, and favourites with paginated results.

Instructions

List a manga's characters. Returns a manga's cast (character name, native name, billed role, image, favourites), paginated. The AniList id space is shared between anime and manga but the two do not overlap, so an anime id here returns 404 -- use GET /anime/title/{id}/characters for those.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "manga_title_characters"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	AniList manga id
`page`	No	1-based page number, default 1
`per_page`	No	Results per page, default 10, max 50

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.2Sep 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses pagination, the exact cast fields returned, and the 404 behavior for anime ids. It stops short of covering auth or rate limits, so not quite a 5.

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?

Three sentences, front-loaded with the action and return contents, then the id-space caveat. No filler, and the most error-prone detail (id namespace collision) is given its own clause.

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?

No output schema exists, so the description correctly explains the return shape and pagination, and even pre-empts the most likely failure mode. Nothing needed to call it correctly is missing.

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%, so id, page, and per_page are already documented with defaults and max. The description only references pagination generically and adds no syntax or format detail beyond the schema; 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?

States a specific verb and resource ('List a manga's characters') and enumerates the returned fields, which cleanly separates it from manga_title_staff and anime_title_characters. An agent can identify the tool's function without opening the 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?

Explicitly names the alternative and the selecting condition: an anime id returns 404 here, so use GET /anime/title/{id}/characters instead. This is the when-not-to-use guidance most definitions lack.

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

Deploy Server