Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

manga_search

Search manga by free-text query and return normalized AniList entries with titles, scores, popularity, format, status, chapters, volumes, genres, and tags.

Instructions

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

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.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 provided, so the description carries the full burden. It adds useful context: 'Credential-free public manga data from AniList' and lists the returned normalized fields. However, it does not disclose behaviors like default pagination, default sort order, or explicitly state that the tool is read-only (though 'search' implies it). This is adequate but not comprehensive.

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 concise, with the purpose front-loaded and additional details (data source, return fields) presented efficiently. It is not overly verbose and every sentence contributes value, though it could be slightly more crisp by naming alternatives.

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 there is no output schema, the description lists the return fields (titles, scores, popularity, etc.), which is helpful. However, it does not mention pagination behavior, default sort, or provide guidance on when to use this search tool versus specific title/ranking tools. The schema covers parameter details, but the description lacks explicit context about alternatives and response characteristics.

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% – all parameters (query, page, sort, per_page) have descriptions. The description adds no extra meaning beyond what the schema already provides, such as clarifying sort values or pagination defaults. It does mention 'free-text query' which aligns with the query parameter but adds no new information.

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 clearly states the tool searches manga by free-text query, with a specific verb and resource. It also lists the return fields (titles, scores, popularity, etc.). However, it does not explicitly differentiate from sibling tools like manga_title or manga_rankings, relying on the name and general search context to distinguish.

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 implies usage for free-text search ('Searches manga by free-text query') but provides no explicit guidance on when to use this tool versus alternatives like manga_title for specific lookups or anime_search for anime. There are no when-not conditions or alternative tool names mentioned, so the agent must infer usage.

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