Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

manga_rankings

Retrieve filterable, sorted manga rankings from public AniList data. Filter by format, genre, or status to find trending or popular titles.

Instructions

Rank manga. Returns a filterable, sorted manga ranking. Credential-free public AniList data. Filter by format, genre, and status.

Input Schema

TableJSON 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

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 burden. It discloses that the data is 'Credential-free public AniList data', indicating no authentication is needed and the operation is read-only. It does not describe pagination behavior, default sort, or output structure, but for a simple ranking endpoint this is a reasonable amount of behavioral context. No contradictions.

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 short sentences, front-loaded with the core action. 'Rank manga' is somewhat redundant with the tool name, but the rest of the description adds useful context about data source and filtering. No wasted words.

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 read-only ranking tool with six optional parameters and no output schema, the description covers the data source, filtering capabilities, and sorting. It does not mention pagination or defaults, but those are in the schema. It is complete enough for an agent to decide to invoke it, though it could note that all parameters are optional and that it returns a list.

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 the schema already documents all six parameters. The description mentions the filter dimensions (format, genre, status) but adds no detail beyond the schema's parameter descriptions. 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 action ('Rank manga') and resource, and clarifies it returns a 'filterable, sorted manga ranking'. It clearly distinguishes itself from sibling tools like manga_search and manga_title by focusing on rankings, and from anime_rankings by specifying manga. The purpose is unambiguous.

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 description notes it uses 'Credential-free public AniList data' and can be filtered by format, genre, and status, which implies it is for retrieving ranked manga lists rather than searching or fetching details. However, it does not explicitly state when to prefer this over manga_search or anime_rankings, nor any exclusions. Usage context is implied, not explicit.

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