Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

manga_rankings

Rank manga from AniList by trending, popularity, score, favorites, or release date, and filter results by format, genre, or status.

Instructions

Rank manga. Returns a ranked list of manga from AniList. sort defaults to TRENDING_DESC; other values are POPULARITY_DESC, SCORE_DESC, FAVOURITES_DESC, START_DATE_DESC and UPDATED_AT_DESC. Filter by format, genre or status. Paged with page (default 1) and per_page (default 20, max 50); has_next_page shows if more exist.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number, default 1
sortNoOrder: TRENDING_DESC, POPULARITY_DESC, SCORE_DESC, FAVOURITES_DESC, START_DATE_DESC, UPDATED_AT_DESC. Default TRENDING_DESC.
genreNoGenre filter, e.g. Fantasy.
formatNoFormat filter: MANGA, NOVEL, ONE_SHOT.
statusNoStatus filter: FINISHED, RELEASING, NOT_YET_RELEASED, CANCELLED, HIATUS.
per_pageNoResults per page, default 20, max 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / format / enum
      Added value: +[
+  "MANGA",
+  "NOVEL",
+  "ONE_SHOT"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "TRENDING_DESC",
+  "POPULARITY_DESC",
+  "SCORE_DESC",
+  "FAVOURITES_DESC",
+  "START_DATE_DESC",
+  "UPDATED_AT_DESC"
+]
    • addedInput schema / properties / status / enum
      Added value: +[
+  "FINISHED",
+  "RELEASING",
+  "NOT_YET_RELEASED",
+  "CANCELLED",
+  "HIATUS"
+]
  2. Addedv1.5.0

TDQS

B3.2/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 useful behavioral context — the data source (AniList), the pagination model (page/per_page with max 50), and the return-side field has_next_page. But it says nothing about rate limits, auth requirements, or the shape of each ranked entry, and several details (defaults, enum values) merely repeat the schema.

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 and result, then filters, then paging — a sensible order with no filler sentences. It loses a point for enumerating sort/page defaults that duplicate the schema verbatim, which adds length without new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 is the only source of return-value information, and it only says 'ranked list' plus has_next_page. It never describes what fields each ranked manga contains, which is a meaningful gap for an agent deciding how to use the results, though the parameter coverage is otherwise adequate.

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 coverage is 100%, so the schema already documents all six parameters including defaults and enum values. The description largely restates those (sort default and values, page/per_page defaults) and adds no format or syntax detail for the free-form genre filter beyond the schema's 'Fantasy' example. Baseline 3 applies.

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 ('Rank manga') and identifies the data source ('Returns a ranked list of manga from AniList'), which is clearer than the bare name. However, it never explicitly distinguishes itself from close siblings such as manga_search or anime_rankings, so the agent must infer that this is a ranking/browse endpoint rather than a search.

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

Usage Guidelines2/5

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

The description lists filterable fields ('Filter by format, genre or status') but gives no when-to-use vs when-not guidance and never names an alternative tool. An agent cannot tell from the text whether to call this or manga_search for a given intent.

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