Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

anime_title

Fetch anime details by AniList ID, including titles, scores, genres, studios, images, and airing countdown. Enable MAL enrichment to add MyAnimeList community scores.

Instructions

Get an anime. Returns an anime by AniList id: titles (romaji/english/native), MyAnimeList id, scores, popularity, favourites, format, status, season, episodes, duration, genres, ranked tags, studios, dates, description, images, and next-airing countdown. 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 anime 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.6.0
  2. Removedv1.6.0
  3. Addedv1.5.0

TDQS

A3.6/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 discloses that mal=true triggers an extra fetch and describes the resulting mal block, but says nothing about error behavior for an invalid id, read-only safety, or rate limits.

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 verb and resource, then the return-field enumeration, then the mal flag. The middle list is long but earns its place since no output schema exists; nothing is redundant.

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?

For a 2-parameter lookup with no output schema and no annotations, enumerating the returned fields plus the optional mal block gives the agent enough to call it correctly. Only explicit sibling routing for id discovery 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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by spelling out what the mal enrichment actually yields (MAL community score on a 0-10 scale plus scored-by count), which the input schema does not convey.

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+resource ('Get an anime... Returns an anime by AniList id'), and the 'by AniList id' qualifier implicitly separates it from a search-based sibling. It stops short of naming anime_search as the alternative, so it is clear but not sibling-differentiating.

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?

Usage is only implied: the agent infers it must already hold an AniList id and that mal=true is optional. There is no explicit when-to-use/when-not guidance and no routing to anime_search for agents that don't yet have an id.

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