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 to retrieve titles, scores, popularity, format, status, chapters, volumes, genres, and tags.

Instructions

Search manga. Searches manga by free-text query. Returns entries: titles, scores, popularity, format, status, chapters, volumes, genres, and tags.

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.5.0

TDQS

B3.2/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 fields returned (titles, scores, popularity, format, status, chapters, volumes, genres, tags), which matters because there is no output schema, but it says nothing about pagination behavior, total-result limits, or auth/rate constraints.

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?

Short and front-loaded, with the core action in the first two words. The first two sentences are somewhat redundant ('Search manga' / 'Searches manga by free-text query'), which costs it a point, but there is no padding.

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?

With no output schema, the description's field list is a genuine contribution and covers the return shape. However, it omits result-set behavior (total counts, how to page through everything) and gives no routing to sibling tools, leaving a search tool that is adequate but not complete.

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 (with max 50) and the sort enum. The description adds no syntax, default, or format detail beyond what the schema provides, 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 and resource ('Search manga', 'Searches manga by free-text query') and enumerates the returned fields, so an agent knows what it does. It does not, however, distinguish itself from siblings like manga_title or manga_rankings, so the agent must infer that this is the free-text entry point.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives; the description never says to use manga_title for a known ID or manga_rankings for ranked lists. Usage is only implied by the word 'Search' and the presence of a query parameter.

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