Skip to main content
Glama

Search manga

search_manga
Read-only

Search MyAnimeList for manga, light novels, manhwa, and manhua by keyword. Returns compact results with mal_id for further actions, with filters for type, genre, status, and more.

Instructions

Search MyAnimeList manga by keyword (also light novels, manhwa/manhua); returns compact summaries with the mal_id that other manga tools require.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query, e.g. a manga title.
sfwNoIf true, exclude adult (NSFW) entries. Defaults to false (no filtering).
pageNo1-based page number for pagination.
sortNoSort direction.
typeNoFilter by publication type.
limitNoMax results per page (1-25).
genresNoComma-separated Jikan genre IDs.
statusNoFilter by publication status.
order_byNoField to order by.
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds that it returns compact summaries with mal_id, which is useful but does not disclose pagination or ordering defaults. No contradictions.

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?

Single sentence, front-loaded with action and scope, no wasted words. Efficient and clear.

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?

Given 9 parameters, full schema coverage, and no output schema, the description is adequate. It explains the return value (compact summaries with mal_id) and the tool's purpose. Missing explicit pagination info, but acceptable.

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?

All 9 parameters are fully described in the input schema (100% coverage). Description adds no extra meaning beyond what schema already provides, so 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?

Clearly states action (Search), resource (MyAnimeList manga), and scope (also light novels, manhwa/manhua). Distinguishes from 'get_manga' by mentioning returns compact summaries with mal_id needed by other tools.

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?

Implies usage for finding mal_ids for other manga tools, but no explicit when-to-use vs. alternatives like search_anime or get_manga. No when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grinv/mal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server