Skip to main content
Glama
Grinv

MAL MCP Server

Get manga details

get_manga
Read-only

Retrieve comprehensive manga details including synopsis, score, genres, authors, serialization, external links, alternate titles, and related entries by providing a MyAnimeList numeric ID.

Instructions

Get full details for one manga by mal_id: synopsis, score, genres, authors, serialization, external links (official site, social media), alternate title synonyms, and related entries. Obtain the mal_id from search_manga first. sfw/sfw_strict don't affect this manga itself (its id was requested explicitly) — they filter NSFW entries out of its relations list. If Tenrai is unavailable and MAL_CLIENT_ID is set, transparently retries via the official API, which omits favorites/explicit_genres/external (no equivalent field there) and ignores sfw/sfw_strict entirely.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMyAnimeList numeric ID.
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.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
rankNo
typeNo
scoreNo
titleNo
genresNo
mal_idYes
statusNo
themesNo
authorsNo
membersNo
volumesNo
chaptersNo
externalNo
synopsisNo
favoritesNo
image_urlNo
publishedNo
relationsNo
scored_byNo
backgroundNo
popularityNo
publishingNo
demographicsNo
title_englishNo
serializationsNo
title_japaneseNo
title_synonymsNo
explicit_genresNo
Behavior5/5

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

Discloses transparent retry via official API, omitting certain fields and ignoring sfw flags. Annotations (readOnlyHint, openWorldHint) are consistent and description adds useful context beyond them.

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?

Very concise yet informative. Front-loaded with main purpose, followed by necessary details. No redundant sentences.

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?

Covers all aspects: purpose, prerequisite, parameter effects, fallback behavior, limitations. Output schema exists so return values not needed. Complete for the tool.

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 3. Description adds value: explains id as mal_id and how to obtain it, and clarifies sfw/sfw_strict filter only relations. Surpasses baseline.

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 it gets full details for one manga by mal_id, listing contents (synopsis, score, genres, etc.). Distinguishes from sibling tools like search_manga for ID lookup and get_anime for anime.

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 says to obtain mal_id from search_manga first. Explains sfw/sfw_strict effects only on relations, and notes fallback behavior when Tenrai is unavailable, including limitations.

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