Skip to main content
Glama

Search anime

search_anime
Read-only

Find anime by keyword on MyAnimeList. Receive compact summaries with IDs and pagination details.

Instructions

Search MyAnimeList anime by keyword; returns compact summaries (with the mal_id that other anime tools require) plus pagination info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query, e.g. an anime title.
sfwNoIf true, exclude adult (NSFW) entries. Defaults to false (no filtering).
pageNo1-based page number for pagination.
sortNoSort direction.
typeNoFilter by media type.
limitNoMax results per page (1-25).
genresNoComma-separated Jikan genre IDs, e.g. '1,4'.
statusNoFilter by airing 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. The description adds that it returns compact summaries and pagination info, adding some context but not significantly beyond annotations.

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?

The description is a single sentence that is front-loaded with the verb and action, conveying the core purpose without waste.

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 and no output schema, the description explains the return type (compact summaries with mal_id, pagination info) which is helpful but could be more detailed about the structure.

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 coverage is 100% with descriptions for all 9 parameters. The description does not add additional meaning to parameters beyond indicating keyword search, 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?

The description clearly states the verb (search), resource (MyAnimeList anime), and what it returns (compact summaries with mal_id). It also distinguishes from siblings by noting that the mal_id is required by other anime tools.

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 implies usage by mentioning that the returned mal_id is needed by other anime tools, suggesting this tool is for finding anime to use with those tools. However, it does not explicitly state when not to use or provide alternatives among siblings.

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