MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Browse interest stacks

get_interest_stacks

Read-only

Browse or search user-curated MyAnimeList Interest Stacks to discover themed anime and manga lists for mood- or taste-based requests, then fetch a stack by ID for its entries.

Instructions

Browse or search MyAnimeList Interest Stacks: themed anime/manga lists curated by real users, each entry carrying the curator's own score and note. Use this for taste- or mood-shaped requests ('something melancholy', 'cozy slice-of-life') where a ranking or a genre filter is the wrong instrument — get_top_anime answers 'what is best', this answers 'what goes together'. Returns stack metadata only; pass a stack's mal_id to get_interest_stack for its actual entries. For stacks containing one specific title, use get_anime_interest_stacks/get_manga_interest_stacks instead. No official-API fallback exists for this tool — it always needs Tenrai itself to be reachable.

Input Schema

Name	Required	Description
`q`	No	Free-text search over stack titles and descriptions. Omit to browse all.
`sfw`	No	If 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.
`page`	No	1-based page number for pagination (1-20000).
`sort`	No	Sort direction. Only takes effect together with `order_by`; ignored on its own.
`limit`	No	Max results per page (1-100).
`official`	No	Filter by official MAL-editorial stacks. 'true' includes them alongside the rest, 'false' (default) excludes them, 'only' returns exclusively those.
`order_by`	No	Field to order by. Defaults to created_at (newest stacks first).
`spoilers`	No	Filter by stacks flagged as containing spoilers. 'true' includes them alongside the rest, 'false' (default) excludes them, 'only' returns exclusively those.
`challenges`	No	Filter by challenge stacks (watch-along style lists). 'true' includes them alongside the rest, 'false' (default) excludes them, 'only' returns exclusively those.
`sfw_strict`	No	If 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.
`stack_type`	No	Restrict to anime stacks or manga stacks. Omit for both.

Output Schema

Name	Required	Description	Default
`page`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.11.0Oct 25, 2026

changedInput schema / properties / challenges / description

Previous value: -"Filter by challenge stacks (watch-along style lists). 'true' includes them alongside the rest (default), 'false' excludes them, 'only' returns exclusively those."New value: +"Filter by challenge stacks (watch-along style lists). 'true' includes them alongside the rest, 'false' (default) excludes them, 'only' returns exclusively those."

changedInput schema / properties / limit / description

Previous value: -"Max results per page (1-50)."New value: +"Max results per page (1-100)."

changedInput schema / properties / limit / maximum
```
Previous value: -50New value: +100
```

changedInput schema / properties / official / description

Previous value: -"Filter by official MAL-editorial stacks. 'true' includes them alongside the rest (default), 'false' excludes them, 'only' returns exclusively those."New value: +"Filter by official MAL-editorial stacks. 'true' includes them alongside the rest, 'false' (default) excludes them, 'only' returns exclusively those."

changedInput schema / properties / page / description

Previous value: -"1-based page number for pagination (1-1000)."New value: +"1-based page number for pagination (1-20000)."

changedInput schema / properties / page / maximum
```
Previous value: -1000New value: +20000
```
addedInput schema / properties / q / maxLength
```
Added value: +300
```

changedInput schema / properties / sort / description

Previous value: -"Sort direction."New value: +"Sort direction. Only takes effect together with `order_by`; ignored on its own."

changedInput schema / properties / spoilers / description

Previous value: -"Filter by stacks flagged as containing spoilers. 'true' includes them alongside the rest (default), 'false' excludes them, 'only' returns exclusively those."New value: +"Filter by stacks flagged as containing spoilers. 'true' includes them alongside the rest, 'false' (default) excludes them, 'only' returns exclusively those."

Addedv0.10.0Aug 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover read-only and open-world nature, and the description adds the non-obvious operational facts: it returns stack metadata only (not entries), and it has no official-API fallback so Tenrai must be reachable. That availability constraint is exactly the kind of behavior an agent cannot infer from structured fields and would otherwise discover only by failing.

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?

Purpose and the routing contrast to get_top_anime land in the first two sentences; the metadata-only caveat, per-title alternatives, and availability dependency follow in dependency order. The illustrative mood examples are compact and directly serve tool selection rather than padding.

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?

For an 11-parameter browse tool with an output schema, the description covers what an agent still needs: what family of tool this belongs to, the return-shape boundary (metadata vs entries), the two-step path to actual entries, and the availability prerequisite. Nothing required for a correct call is missing or left to inference.

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?

With 11 parameters at 100% schema description coverage, the schema already documents search, pagination, sorting, and every filter enum in detail. The description only implies the browse-vs-search distinction ('Browse or search') and adds no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb pair (browse/search) and a specific resource (MyAnimeList Interest Stacks), then defines what the resource actually is: user-curated themed anime/manga lists with per-entry curator scores and notes. This is clearly separable from get_top_anime, search_anime, and get_interest_stack without opening any schema.

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?

Gives an explicit trigger class ('taste- or mood-shaped requests' such as 'something melancholy' or 'cozy slice-of-life') plus the negative case where a ranking or genre filter is the wrong instrument. It also names three alternatives with the conditions selecting them: get_top_anime for 'what is best', get_interest_stack for a stack's entries, and get_anime_interest_stacks/get_manga_interest_stacks for one specific title.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server