Skip to main content
Glama
Grinv

MAL MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get interest stacks containing an anime

get_anime_interest_stacks
Read-only

List public MyAnimeList Interest Stacks that include a given anime ID, helping you see what people group it with and start human-curated recommendations without relying on vote counts.

Instructions

List the public MyAnimeList Interest Stacks that include a given anime (by mal_id) — useful for 'what do people group this with' and as a jumping-off point for recommendations rooted in human curation rather than vote counts. Get the mal_id from search_anime. Returns stack metadata only; pass a stack's own mal_id to get_interest_stack for its entries. No official-API fallback exists for this tool — it always needs Tenrai itself to be reachable.

Input 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.
pageNo1-based page number for pagination (1-20000).
sortNoSort direction. Only takes effect together with `order_by`; ignored on its own.
limitNoMax results per page (1-100).
officialNoFilter by official MAL-editorial stacks. 'true' includes them alongside the rest, 'false' (default) excludes them, 'only' returns exclusively those.
order_byNoField to order by. Defaults to created_at (newest stacks first).
spoilersNoFilter by stacks flagged as containing spoilers. 'true' includes them alongside the rest, 'false' (default) excludes them, 'only' returns exclusively those.
challengesNoFilter by challenge stacks (watch-along style lists). 'true' includes them alongside the rest, 'false' (default) excludes them, 'only' returns exclusively 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

NameRequiredDescriptionDefault
pageYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.11.0
    • 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
    • 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."
  2. Addedv0.10.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only and open-world semantics, so the description's added value is the disclosure that it returns stack metadata only and that no official-API fallback exists, meaning Tenrai must be reachable. That availability caveat is genuinely useful, though it does not cover result volume or failure behavior.

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

Conciseness4/5

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

Front-loaded with the verb and resource, then prerequisites, return scope, and availability caveat in a logical order. It is a bit dense at three clauses plus a caveat, but nearly every sentence carries actionable information.

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?

With an output schema present and full parameter coverage, the description only needs to frame purpose, routing, and caveats, which it does. Only minor gaps remain, such as how large result sets are returned in practice.

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 description coverage is 100%, so all ten parameters (sfw vs sfw_strict, official/spoilers/challenges tri-state enums, order_by/sort interaction) are already documented in the schema. The description adds only the origin of the required id; 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 (List) and resource (public MyAnimeList Interest Stacks) plus the binding scope (that include a given anime by mal_id). It is clearly distinguishable from get_interest_stack (which returns entries of one stack) and get_manga_interest_stacks (the manga counterpart), both of which are named or implied in the routing sentence.

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 use case ('what do people group this with', human-curated recommendations vs vote counts), a prerequisite ('Get the mal_id from search_anime'), and a handoff rule ('pass a stack's own mal_id to get_interest_stack'). An agent knows when to call this and what to do next.

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

Deploy Server

Other Tools