Skip to main content
Glama
Sign In
MyAnimeList MCP Server

MyAnimeList MCP Server

by MorpKnight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_manga_list

Retrieve a MyAnimeList user's manga list, with support for status filters, sorting, and pagination.

Instructions

Fetch a manga list for a MAL user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>",
      "status": "<status>"
    },
    "name": "get_manga_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNoNumber of results
offsetNoPagination offset
statusYes
usernameYesMyAnimeList username

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations are absent, so the description carries the full burden. 'Fetch' indicates a read-only operation, but it does not disclose potential issues such as private lists, rate limits, or pagination behavior. It is minimally transparent but not misleading.

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?

The description is a single, direct sentence with no filler. It is appropriately sized for a minimal tool description, earning a 5 for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 5 parameters, no output schema, and no annotations, a one-sentence description is insufficient. It does not explain the required status filter, pagination options, or return value structure, making it hard for an agent to use correctly.

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 coverage is 60% with descriptions for limit, offset, and username. The description adds no parameter semantics beyond the schema, and status/sort lack explicit descriptions. Baseline applies since the schema covers the majority of parameters.

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 clearly states 'Fetch a manga list for a MAL user' – a specific verb and resource. It distinguishes from sibling tools like get_manga or get_anime_list by indicating a manga-specific user list, though it does not explicitly contrast with get_anime_list.

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

Usage Guidelines2/5

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

No information is provided about when to use this tool versus alternatives. The description does not mention prerequisites, such as requiring a valid username or that status is a required filter, nor does it refer users to sibling tools for other list types.

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

Deploy Server

Other Tools