Skip to main content
Glama
Grinv

AniList MCP Server

Get the anime airing schedule

get_anime_schedule
Read-only

Retrieve upcoming anime episode air times. Get the site-wide schedule or filter by a specific title for its next episode air date.

Instructions

Get upcoming (or a specific title's) episode air times. Omit mediaId for the site-wide upcoming schedule, or pass it (from search_media/get_media) to get one title's next-episode air time. Anime only — manga has no airing schedule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination.
mediaIdNoRestrict to this AniList anime ID.
perPageNoResults per page (max 25).
notYetAiredNoSet false to include already-aired episodes too.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
scheduleYes
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint; description adds context about upcoming episodes and anime-only limitation, but does not elaborate on pagination behavior or rate limits. No contradiction with annotations.

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?

Two well-structured sentences, front-loaded with core purpose, no redundant information.

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's 4 parameters, output schema, and annotations, the description fully covers usage scenarios, parameter roles, and constraints.

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 meaningful guidance on mediaId usage and pagination hint, going beyond schema descriptions.

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 'Get upcoming (or a specific title's) episode air times' with specific verb and resource, and differentiates from sibling tools by referencing search_media/get_media.

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 explains when to omit or include mediaId for site-wide vs specific title, and warns that manga has no airing schedule, providing clear usage boundaries.

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/anilist-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server