Skip to main content
Glama
Grinv

MAL MCP Server

Search manga

search_manga
Read-only

Search manga on MyAnimeList using keywords. Returns compact summaries and mal_ids for use with other manga tools.

Instructions

Search MyAnimeList manga by keyword (also light novels, manhwa/manhua); returns compact summaries with the mal_id that other manga tools require. If Tenrai is unavailable and MAL_CLIENT_ID is set, transparently retries via the official API, which ignores every filter except q/sfw/limit/page (type/status/genres/genres_exclude/score/min_score/max_score/letter/magazines/start_date/end_date/unapproved/order_by/sort are silently dropped), always returns empty themes/demographics (no official-API equivalent), enforces an explicit sfw: true client-side (a filtered page can come back shorter than limit), and — for a query with no real title match — comes back with a page of unrelated manga instead of an empty result (a quirk of the official search endpoint itself, not a mal-mcp bug; don't treat a nonsense-query result as a real match during a fallback).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query, e.g. a manga title.
sfwNoIf true, exclude adult/explicit-rated entries (R+ Mild Nudity and up). Defaults to false (no filtering). Note: this alone still allows mainstream, safely-rated shows tagged with the Ecchi genre (fanservice) through — use `sfw_strict` to also exclude those.
pageNo1-based page number for pagination (1-1000).
sortNoSort direction.
typeNoRestrict to one or more publication types.
limitNoMax results per page (1-50).
scoreNoRestrict to entries with exactly this average score (rarely useful — prefer min_score/max_score for a range).
genresNoComma-separated MAL genre IDs to include (max 25), e.g. '1,4'. Look up IDs with get_manga_genres.
letterNoRestrict results to entries whose title starts with this single letter.
statusNoFilter by publication status.
end_dateNoOnly include entries whose end date is on or before this date (YYYY-MM-DD).
order_byNoField to order by.
magazinesNoComma-separated MAL magazine IDs to restrict to (max 25). Look up IDs with get_magazines.
max_scoreNoMaximum average MAL score (inclusive), 1-10.
min_scoreNoMinimum average MAL score (inclusive), 0-10.
sfw_strictNoIf true, exclude adult/explicit-rated entries AND anything tagged with the Ecchi genre, even otherwise-mainstream/safely-rated shows. Stricter than `sfw` alone. Defaults to false.
start_dateNoOnly include entries whose start date is on or after this date (YYYY-MM-DD).
unapprovedNoIf true, also include entries not yet approved by MAL's moderators (excluded by default). Defaults to false.
genres_excludeNoComma-separated MAL genre IDs to exclude (max 25), e.g. '1,4'. Look up IDs with get_manga_genres.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
resultsYes
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint), the description details transparent retry, parameter dropping, empty fields, client-side sfw enforcement, and a quirk where nonsense queries return unrelated results. This adds significant behavioral context.

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?

While lengthy (250+ words), the description is well-structured with front-loaded purpose and detailed fallback notes. Every sentence serves a purpose given the tool's complexity, though some brevity could be gained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (19 parameters, fallback behavior), the description covers edge cases (nonsense queries, filter dropping, empty themes/demographics) and references an output schema. It is comprehensive without needing extra explanation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 19 parameters (100% coverage). The description adds value by noting which parameters are ignored during fallback, which is beyond the schema definitions, providing practical guidance for parameter use.

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 clearly states it searches MyAnimeList manga (and light novels, manhwa, manhua) by keyword, and returns compact summaries with mal_id needed by other tools. This distinguishes it from siblings like search_anime (for anime) and get_manga (by ID).

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 explains fallback behavior when Tenrai is unavailable and which parameters are ignored, providing context for when to use the tool. However, it does not explicitly state when not to use it or compare to alternatives like search_anime.

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