Skip to main content
Glama
nicoaguerrero

MyAnimeList MCP Server

by nicoaguerrero
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_manga_details

Fetch detailed manga information from MyAnimeList by ID. Choose specific fields such as score, genres, synopsis, or recommendations.

Instructions

    Fetches details of a manga by its ID from MyAnimeList.
    
    Args:
        manga_id (int): The ID of the manga to fetch details for.
        fields (List[str]): List of fields to include in the response. If None, includes common fields:
            id, title, main_picture.
            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_volumes, num_chapters, authors, pictures,
            background, related_anime, related_manga, recommendations, serialization
    
    Examples:
    - To get the score: get_manga_details(30230, fields=["mean"])
    - To get similar mangas: get_manga_details(30230, fields=["recommendations"])
    - To get genres and synopsis: get_manga_details(30230, fields=["genres", "synopsis"])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
manga_idYes
fieldsYes

Tool Definition Quality

A4.1/5.0
Behavior3/5

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

No annotations provided. Description states it fetches data, mentions optional fields with defaults, and lists valid fields. Missing info on error handling, authorization (likely none), rate limits, or whether it modifies data. Adequate for a read operation but could be more exhaustive.

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?

Well-structured with separate sections for general description, args, and examples. A bit verbose due to full field list and multiple examples, but each part adds value. The 'Args:' header is redundant given the schema, but overall concise enough.

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 low complexity (2 params, no output schema), description covers purpose, parameters, and usage patterns via examples. Lacks explicit mention of response structure (e.g., JSON object containing requested fields), but the field list implies the shape. Sufficient for basic 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?

Schema description coverage is 0%, but description explains both parameters: manga_id as the ID, fields as a list with default behavior (if None, includes common fields) and enumerated valid values. Adds significant meaning beyond schema types, though format of fields list (e.g., comma-separated) could be clarified.

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?

Description clearly states 'Fetches details of a manga by its ID from MyAnimeList.' Specific verb ('fetches') and resource ('details of a manga') with source mentioned, distinguishing it from sibling tools like 'get_manga' (list mangas) and 'get_anime_details' (anime resource).

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?

Examples show specific use cases (score, recommendations, genres). No explicit when-not or alternatives, but the context of fetching by ID implies it's for individual manga details, not bulk operations. Clear enough for the task.

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