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, or favorites using filterable public AniList data; filter by season, year, format, genre, and status to return sorted results.

Instructions

Rank anime. Returns a filterable, sorted anime ranking. Credential-free public AniList data. Filter by season, year, 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: 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

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description carries the burden. It discloses 'Credential-free public AniList data,' a useful behavioral trait. However, it doesn't explicitly state read-only behavior, response shape, or pagination beyond what the schema already provides.

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?

Four short sentences with key facts front-loaded; 'Rank anime' is slightly redundant with the following sentence, but the description overall is minimal and focused.

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?

Given 8 optional params, full schema coverage, and no output schema, the description covers the operation and filters but does not describe the shape of the returned ranking or item fields, which would help an agent.

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 documents all 8 parameters. The description's 'Filter by season, year, format, genre, and status' restates the filter parameters without adding new semantics beyond the schema.

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 anime' and clarifies it returns a 'filterable, sorted anime ranking.' The resource 'anime' distinguishes it from siblings like manga_rankings, though it doesn't explicitly name alternatives.

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?

Provides implied context ('Credential-free public AniList data', filters) but no explicit when-to-use or alternative routing. An agent can infer it's for obtaining anime rankings, but there is no guidance on preferring it over anime_search or anime_title.

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