Skip to main content
Glama

Search Manga

search_manga
Read-only

Find manga by title in MyAnimeList's public catalog. Returns details including year, type, score, chapters, and genres.

Instructions

Search MyAnimeList's public manga catalog by title.

Returns a compact text table (id|title|year|type|mean|chapters|genres) plus structured content {"count": int, "results": [...]} where each result has: id, title, picture, year, media_type (manga/novel/one_shot/...), publishing_status, mean (community score), num_chapters/num_volumes (0 = unknown/ongoing), genres, authors, and a synopsis truncated to 300 characters. Use get_manga_detail for full information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return
queryYesTitle to search for (MAL needs ~3+ characters)
Behavior5/5

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

Exceeds annotations by detailing output format: compact text table and structured content with fields listed. Notes that num_chapters/volumes = 0 indicates unknown/ongoing, and synopsis truncated to 300 characters. No contradiction with readOnlyHint or openWorldHint.

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 sentences: first states purpose, second describes output, third directs to sibling. Every sentence adds value. Concise and well-structured.

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?

With no output schema, the description fully explains the return format, including both text table and structured data with all key fields. Provides completeness for a search tool by covering response shape and special values.

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 coverage is 100%, so baseline is 3. Description adds value by explaining the query parameter expects a title and notes the '~3+ characters' requirement. The limit parameter is implicitly mentioned via default, but not elaborated beyond schema.

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 the verb 'search' and resource 'MyAnimeList's public manga catalog by title'. Distinguishes from sibling 'search_anime' and mentions alternative 'get_manga_detail' for full info.

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

Usage Guidelines5/5

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

Explicitly states when to use: search by title. Provides a prerequisite that 'MAL needs ~3+ characters' for the query parameter. Contrasts with 'get_manga_detail' for full information, guiding the agent on tool selection.

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/UmutKDev/myanimelist-mcp'

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