Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

manga_title_recommendations

Get titles AniList users recommend alongside a manga, ordered by recommendation count, each with community rating and full title data.

Instructions

List titles recommended alongside a manga. Returns the titles AniList users recommend alongside a manga, most-recommended first, each with its community rating and full title record. Recommendations can cross media types -- a manga's list may include anime -- so read each entry's own type rather than assuming manga. An anime id here returns 404 -- use GET /anime/title/{id}/recommendations 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.4/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 disclose meaningful behavior: result ordering (most-recommended first), the per-entry payload (community rating plus full title record), the cross-media caveat, and the 404 failure mode. It omits auth requirements, rate limits, and pagination semantics, so it falls short of fully covering a mutation-free but non-trivial read tool.

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?

Three sentences, front-loaded with the core purpose and zero filler; the cross-media warning and the 404 routing note each carry weight. Slightly long but every clause is doing work.

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?

There is no output schema, so the description must characterize return values, and it does: ordering, per-entry fields, and the mixed-media caveat. Combined with 100% schema coverage on inputs, an agent has everything needed to call this correctly.

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%, including the 'AniList manga id' hint, so the schema already documents every parameter. The description adds no format, range, or unit detail beyond what the schema states, so the baseline 3 applies.

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 a specific verb and resource ('List titles recommended alongside a manga') and immediately identifies the sibling it is not by naming the anime variant and its path. An agent can distinguish this from anime_title_recommendations and the other manga_title_* tools 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?

It gives an explicit negative condition ('An anime id here returns 404') paired with the exact alternative to use instead, which is precisely the routing information an agent needs. For non-anime ids, the intended use is clear from the lead sentence.

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