Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

manga_title

Fetch detailed manga data by AniList ID, including titles, scores, genres, status, and images; optionally enrich results with MyAnimeList community scores.

Instructions

Get a manga. Returns a manga by AniList id: titles, MyAnimeList id, scores, popularity, favourites, format, status, chapters, volumes, genres, ranked tags, dates, description, and images. Pass mal=true to additionally enrich the response with the MyAnimeList community score (mal block: score on a 0-10 scale, plus scored-by count).

Input Schema

NameRequiredDescriptionDefault
idYesAniList manga id
malNoEnrich with the MyAnimeList community score (adds one fetch; omitted when the title has no MAL id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the shape of the response and that mal adds an extra fetch that is skipped when no MAL id exists, but it says nothing about invalid-id behavior, error handling, or rate limits for a public lookup.

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 purpose, then the return payload, then the optional-flag behavior. The long field list is dense but informative; no sentence is pure filler.

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?

With no output schema, the description's field enumeration effectively documents the return value, and the mal opt-in behavior is fully explained. For a two-parameter read-by-id tool, nothing an agent needs 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline would be 3, but the description goes beyond the schema on mal by explaining what enrichment produces (a mal block with a 0-10 score and scored-by count), which the schema only gestures at.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus the lookup key: "Get a manga ... by AniList id," and enumerates the returned fields. The id-scoping implicitly separates it from manga_search, but no sibling (manga_search, manga_rankings) is named, so the differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage guidance is conditional on a parameter ("Pass mal=true to additionally enrich..."), which is helpful but parameter-level, not tool-level. There is no statement of when to call this versus manga_search or when a lookup is not appropriate.

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