Skip to main content
Glama
Grinv

MAL MCP Server

Get seasonal anime

get_seasonal_anime
Read-only

Retrieve anime list for a specific season and year, or current season if unspecified. Supports filtering by media type, rating, and more.

Instructions

List anime from a given season — supply both year and season together, or omit both for the current season; supplying only one is treated as omitting both. For next season's lineup use get_upcoming_season instead. If Tenrai is unavailable and MAL_CLIENT_ID is set, transparently retries via the official API — filter/rating/unapproved/continuing/kids/order_by/sort are silently dropped (no equivalent there), themes/demographics/broadcast come back empty, an explicit sfw: true is enforced client-side (a filtered page can come back shorter than limit), and sfw_strict degrades to the same filtering as sfw there (no Ecchi-genre distinction available).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
kidsNoIf true, exclude entries tagged as children's/kids content. Defaults to false.
pageNo1-based page number for pagination (1-1000).
sortNoSort direction.
yearNoFour-digit year, e.g. 2024.
limitNoMax results per page (1-50).
filterNoRestrict to one or more media types.
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.
seasonNoSeason name.
order_byNoField to order by. Defaults to members.
continuingNoIf true, also include TV series continuing from a previous season. Defaults to false.
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.
unapprovedNoIf true, also include entries not yet approved by MAL's moderators (excluded by default). Defaults to false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
resultsYes
Behavior5/5

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

Describes the fallback to the official MAL API when Tenrai is unavailable, lists which parameters are silently dropped (filter, rating, etc.), which fields come back empty, and how sfw_strict degrades. This goes well beyond the annotations, fully disclosing behavioral quirks.

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?

The description is long but each part contributes useful information. It is front-loaded with the core purpose and parameter rules, then details edge-case behaviors. Although dense, it avoids redundancy and maintains focus.

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?

Given the tool has 13 parameters, no required fields, and an output schema, the description covers the key complexities: parameter pairing rules, fallback behavior, parameter dropping, and field degradation. It addresses all likely ambiguities, making the description complete for agent use.

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?

With 100% schema coverage, the schema already documents all parameters. The description adds crucial context about the interplay between year and season (must be together or omitted) and the behavior of sfw/sfw_strict, providing extra meaning beyond the schema definitions.

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 starts with 'List anime from a given season' – a specific verb and resource. It clarifies the parameter pairing rule (year+season together or omitted) and distinguishes from get_upcoming_season, making the tool's purpose unmistakable among siblings.

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 states when to supply parameters (both year and season for a specific season, omit both for current) and directs users to get_upcoming_season for the next season, providing clear guidance on when to use this tool vs an alternative.

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