Skip to main content
Glama

Anilist Get Anime

anilist_get_anime
Read-onlyIdempotent

Get full anime details by ID. Returns title, synopsis, episodes, duration, status, score, genres, studios, and season information.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": 21
    },
    "name": "anilist_get_anime"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAniList media ID (e.g. 21 for One Piece, 1 for Cowboy Bebop)

Output Schema

NameRequiredDescriptionDefault
idYesAniList media ID
formatYesAnime format (TV, MOVIE, OVA, ONA, SPECIAL)
genresYesList of genres
seasonYesSeason aired (SPRING, SUMMER, FALL, WINTER)
sourceYesOriginal source (MANGA, LIGHT_NOVEL, VISUAL_NOVEL, etc)
statusYesCurrent status (FINISHED, AIRING, NOT_YET_AIRED, CANCELLED)
studiosYesList of animation studio names
episodesYesTotal episode count
site_urlYesAniList page URL
favouritesYesNumber of times added to favorites
mean_scoreYesMean community score (0-100)
popularityYesPopularity ranking
cover_imageYesURL to cover image
descriptionYesAnime synopsis/description
season_yearYesYear of airing season
title_nativeYesAnime title in native language
title_romajiYesAnime title in Romaji
average_scoreYesAverage community score (0-100)
title_englishYesAnime title in English
duration_minutesYesEpisode duration in minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety and idempotency profile is fully carried by structured data. The description adds the shape of the payload (title, synopsis, episodes, etc.) but says nothing about error behavior for a nonexistent ID, rate limits, or auth. With annotations doing the heavy lifting, this is adequate but not rich.

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 sentences, front-loaded with the operation and followed by the return payload, with no filler or repetition. Every clause carries information the agent can act on.

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?

For a single-parameter lookup with an output schema present, the definition is nearly complete: the agent knows the input type, the exact field set returned, and (via annotations) that the call is a safe, idempotent read. The only omission is fallback behavior when an ID does not resolve, which the output schema may or may not cover.

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%, and the schema itself supplies the semantic anchor with concrete examples ('21 for One Piece, 1 for Cowboy Bebop'). The description's 'by ID' adds nothing beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Get full anime details by ID'), and the 'by ID' qualifier implicitly separates it from the sibling search tool. It also enumerates the returned fields, so the agent knows exactly what data it gets. It stops short of naming the search sibling, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent must infer that this is the right tool when it already has an AniList media ID, and that anilist_search_anime is the path when it only has a title. There is no explicit when-to-use or when-not-to-use statement, and no guidance about what to do if the ID is unknown.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.