Skip to main content
Glama
Grinv

MAL MCP Server

Search anime

search_anime
Read-only

Search MyAnimeList anime by keyword with filters like type, genre, rating, and status. Returns summaries with IDs and pagination info.

Instructions

Search MyAnimeList anime by keyword; returns compact summaries (with the mal_id that other anime tools require) plus pagination info. 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/rating/score/min_score/max_score/letter/producers/start_date/end_date/unapproved/order_by/sort are silently dropped), always returns empty themes/demographics/broadcast (no official-API equivalent for any of these), 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 anime 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. an anime 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 media 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_anime_genres.
letterNoRestrict results to entries whose title starts with this single letter.
ratingNoRestrict to one or more specific content ratings. More granular than `sfw`/`sfw_strict` — use this to target a precise rating band instead of a blanket adult-content cutoff.
statusNoFilter by airing status.
end_dateNoOnly include entries whose end date is on or before this date (YYYY-MM-DD).
order_byNoField to order by.
max_scoreNoMaximum average MAL score (inclusive), 1-10.
min_scoreNoMinimum average MAL score (inclusive), 0-10.
producersNoComma-separated MAL producer/studio IDs to restrict to (max 25). Look up IDs with get_producers.
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_anime_genres.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
resultsYes
Behavior5/5

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

The description extensively discloses behavioral traits: transparent retry via official API with filtered parameters silently dropped, enforced sfw client-side, and nonsense queries returning unrelated anime. This goes far beyond the readOnlyHint and openWorldHint annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and contains multiple paragraphs with detailed fallback behavior, which adds value but could be more concise. The main purpose is front-loaded, but the length may hinder quick comprehension.

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 the complexity (20 parameters, output schema, annotations), the description covers important edge cases and fallback behavior comprehensively. It complements the schema well, though some parameter interactions are only implied in the fallback notes.

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?

The input schema has 100% coverage with individual parameter descriptions, so the tool description does not add much meaning beyond that. It mentions that many filters are ignored during fallback, which is behavioral context rather than parameter-specific semantics.

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?

The description clearly states it searches MyAnimeList anime by keyword and returns compact summaries with mal_id and pagination info. It distinguishes from sibling tools implicitly by specifying 'anime', but does not explicitly differentiate from other search tools like search_manga.

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?

The description implies it is for searching anime, but does not provide explicit guidance on when to use versus alternatives, nor does it mention when not to use it. It only describes behavior during fallback.

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