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 titles, scores, popularity, format, status, season, genres, tags, and studios.

Instructions

Search anime. Searches anime by free-text query. Returns entries: titles, scores, popularity, format, status, season, genres, tags, and studios.

Input 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.6/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 helpfully enumerates the returned fields (titles, scores, popularity, format, status, season, genres, tags, studios), which is genuine behavioral context given there is no output schema, but it says nothing about pagination limits, rate limits, or result caps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action, then the mechanism, then the return shape. 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 4-parameter search tool with no output schema, listing the returned fields meaningfully compensates for the absent output schema. Pagination behavior is covered by the schema, so the description is nearly complete, missing only counting/ranking caveats.

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 query, page, per_page, and the sort enum with defaults. The description adds no parameter-level detail beyond the schema, so the 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 (search) and resource (anime), and distinguishes itself from siblings like anime_rankings, anime_airing_schedule, and anime_title by being the free-text entry point. It does not explicitly name which sibling to prefer, so it falls short of a 5.

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 tool's nature (search by query), but there is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as anime_title for direct lookups or anime_character_search. Adequate but leaves selection to inference.

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