Skip to main content
Glama
nicoaguerrero

MyAnimeList MCP Server

get_anime_details

Retrieve anime details by ID from MyAnimeList, selecting specific fields like score, genres, or recommendations.

Instructions

    Fetches details of an anime by its ID from MyAnimeList.
    
    Args:
        anime_id (int): The ID of the anime to fetch details for.
        fields (List[str]): List of fields to include in the response. If None, includes common fields:
            id, title, main_pictures.
            Valid fields: id, title, main_picture, alternative_titles, start_date, end_date,
            synopsis, mean, rank, popularity, num_list_users, num_scoring_users, nsfw,
            created_at, updated_at, media_type, status, genres, my_list_status, num_episodes,
            start_season, broadcast, source, average_episode_duration, rating, pictures,
            background, related_anime, related_manga, recommendations, studios, statistics.
    
    Examples:
    - To get the score: get_anime_details(30230, fields=["mean"])
    - To get similar animes: get_anime_details(30230, fields=["recommendations"])
    - To get genres and synopsis: get_anime_details(30230, fields=["genres", "synopsis"])
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anime_idYes
fieldsYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It implies a read operation ('Fetches') but does not explicitly state it is read-only, mention rate limits, authentication requirements, or side effects. It does list valid fields and defaults, which adds some behavioral context.

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 well-structured with a clear sentence, parameter docs, and examples. It is front-loaded with the main purpose. However, it is slightly verbose with the full field list, which could be more compact.

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?

Given 2 parameters and no output schema, the description covers purpose, parameters (with defaults and valid values), and examples. It does not describe the response format, which might be inferred from field names, but is otherwise complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description fully compensates. It explains both parameters: anime_id is the ID, and fields is a list of fields to include with a comprehensive list of valid values and default behavior. This adds significant meaning beyond the schema.

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 clearly states the verb 'Fetches' and the resource 'details of an anime by its ID from MyAnimeList'. It distinguishes from siblings like get_anime (which may be simpler) and get_anime_list (list vs detail) through the specificity of fetching detailed fields beyond basic info.

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

Usage Guidelines4/5

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

The description provides explicit usage examples, default field behavior, and lists valid fields, giving clear context. However, it does not explicitly state when to use this tool versus alternatives like get_anime or get_anime_ranking, leaving some ambiguity.

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

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