Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

anime_rankings

Rank anime by trending, popularity, score, favorites, start date, or update time. Filter by season, year, genre, format, and status to get titles, scores, and studios.

Instructions

Rank anime. Ranks anime by sort (default TRENDING_DESC, or POPULARITY_DESC, SCORE_DESC, FAVOURITES_DESC, START_DATE_DESC, UPDATED_AT_DESC). Filter by season, season_year (1940 to 2100), format, genre and status. Paged with page and per_page (default 20, max 50); results carry titles, scores, popularity, episodes, studios and tags.

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: TV, TV_SHORT, MOVIE, SPECIAL, OVA, ONA, MUSIC.
seasonNoAiring season filter: WINTER, SPRING, SUMMER, FALL.
statusNoStatus filter: FINISHED, RELEASING, NOT_YET_RELEASED, CANCELLED, HIATUS.
per_pageNoResults per page, default 20, max 50
season_yearNoAiring year filter, 1940-2100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.17.5
    • addedInput schema / properties / format / enum
      Added value: +[
+  "TV",
+  "TV_SHORT",
+  "MOVIE",
+  "SPECIAL",
+  "OVA",
+  "ONA",
+  "MUSIC"
+]
    • addedInput schema / properties / season / enum
      Added value: +[
+  "WINTER",
+  "SPRING",
+  "SUMMER",
+  "FALL"
+]
    • 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.6.0
  3. Removedv1.6.0
  4. Addedv1.5.0

TDQS

A3.5/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 behavioral burden. It discloses the sort default (TRENDING_DESC), the per_page default (20) and cap (50), and the fields returned. It omits auth requirements, rate limits, or whether the ranking set is bounded/stable — notable gaps for a read-heavy list 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 compact sentences, front-loaded with the core action and then layering sort, filters, and pagination. Dense with no filler, though the opening "Rank anime" is slightly redundant with the sentence that follows it.

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?

With 8 params, no required params, and no output schema, the description usefully summarizes both the query surface (sort/filters/paging) and the return fields. It is nearly self-sufficient, lacking only behavioral caveats like auth or result-set limits.

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 8 parameters with descriptions and enums. The description largely restates the sort enum and per_page/season_year constraints already present in the schema, adding little beyond it. 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?

The description opens with a specific verb+resource ("Rank anime") and enumerates the sorting/filtering dimensions, so an agent knows exactly what it returns. It does not, however, distinguish this from near siblings like manga_rankings or anime_search, which an agent might confuse for the same ranking use case.

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 implied by the sort enum (TRENDING_DESC, POPULARITY_DESC, SCORE_DESC, etc.), which tells the agent this is for ranked/leaderboard-style anime lists. But there is no explicit when-to-use or when-not-to-use guidance, and no sibling alternative (e.g. anime_search for lookup vs this for rankings) is named.

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