Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

anime_search

Search anime by free-text query and retrieve normalized details like titles, scores, popularity, format, status, season, genres, tags, and studios from public AniList data.

Instructions

Search anime. Searches anime by free-text query. Credential-free public anime data from AniList. Returns normalized entries: titles, scores, popularity, format, status, season, genres, tags, and studios.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number, default 1
sortNoOrdering: SEARCH_MATCH, POPULARITY_DESC, SCORE_DESC, TRENDING_DESC, FAVOURITES_DESC, START_DATE_DESC. Default SEARCH_MATCH.
queryYesSearch text
per_pageNoResults per page, default 10, max 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "SEARCH_MATCH",
+  "POPULARITY_DESC",
+  "SCORE_DESC",
+  "TRENDING_DESC",
+  "FAVOURITES_DESC",
+  "START_DATE_DESC"
+]
  2. Addedv1.6.0
  3. Removedv1.6.0
  4. Addedv1.5.0

TDQS

A3.9/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 the data source (AniList), credential-free access, and normalized output fields, which is useful. However, it doesn't mention pagination behavior, rate limits, or what happens on no results. The description does not contradict any annotations (none exist).

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?

The description is compact and front-loaded with the core action. The additional detail on normalized fields is useful but somewhat lists many fields; still, every sentence earns its place for clarity. 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 search tool with 1 required parameter and rich schema descriptions, the description is fairly complete. It names the data source and output structure. Minor gaps: no mention of pagination behavior, sorting default caveats, or error cases, but these are covered by the schema defaults and tool context.

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?

The input schema has 100% coverage with descriptions for query, page, sort, and per_page, including defaults and enum values. The description adds context on the return schema but doesn't add meaning beyond the schema for parameters themselves. Baseline 3 is appropriate.

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 ('Search') and resource ('anime'), plus scope ('free-text query'). It distinguishes itself from sibling tools like anime_title and anime_character_search by describing it as a general search returning normalized entries with specific fields.

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

Usage Guidelines4/5

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

The description indicates it is for free-text queries and lists the return fields, which implies usage for finding anime by keyword. However, it does not explicitly state when to use it versus alternatives like anime_title or anime_rankings, nor any exclusions.

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