Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList user manga list

myanimelist_user_manga_list_list
Read-onlyIdempotent

Retrieve a public MyAnimeList user's manga list with scores, tags, and notes by username; filter by reading status and paginate results with a cursor.

Instructions

List a public MyAnimeList user's manga list with scores, tags and notes. Requires username. Returns a list (use cursor when paginated).

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "myanimelist_user_manga_list_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPass `page.nextCursor` from the previous response to get the next page.
statusNoList status filter: 1 watching/reading, 2 completed, 3 on hold, 4 dropped, 6 planned, 7 all. Default: 7.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
usernameYesRequired. Public MyAnimeList member name, e.g. `TheLlama`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the list must be from a public profile, the response includes scores/tags/notes, and pagination is cursor-driven. It does not cover behavior for private or missing users, which is the main remaining gap.

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?

Three short sentences with the scope constraint and the required parameter front-loaded; nothing is redundant. The parenthetical 'use cursor when paginated' is slightly awkward phrasing but earns its place as a paging hint.

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?

With no output schema, the description correctly notes what is returned (scores, tags, notes) and that results are paginated via cursor. For a six-parameter read-only list tool whose parameters are fully documented in schema, this is close to sufficient; only the status filter and non-public-user behavior go unmentioned.

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%, so every parameter (username pattern, status codes, cursor, context, llm_model, conversation_id) is already documented in the schema. The description only restates that username is required and that cursor drives paging, adding no syntax or semantics beyond the structured fields. Baseline 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?

States a specific verb and resource ('List a public MyAnimeList user's manga list') and enumerates the payload ('scores, tags and notes'), so an agent can distinguish it from myanimelist_user_anime_list_list or myanimelist_manga_get by media type and by user-scoping. It stops short of explicitly naming a sibling it is not, which keeps it at 4 rather than 5.

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?

Gives a hard prerequisite ('Requires `username`') and a pagination instruction ('use cursor when paginated'), which is useful implied guidance. However, there is no statement of when to prefer this over the anime-list or user-activity siblings, and no exclusions or failure conditions.

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