Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList user anime list

myanimelist_user_anime_list_list
Read-onlyIdempotent

Fetch a public MyAnimeList user's anime list with scores, tags, and notes by username, and paginate results using a cursor.

Instructions

List a public MyAnimeList user's anime 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_anime_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, non-destructive, open-world behavior, so the bar is lower. The description still adds real value beyond them: the access restriction to public users, the fields returned, and the pagination mechanism via cursor.

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, front-loaded with the core action and return contents. The "Requires `username`" clause is mildly redundant with the schema's required list, but nothing else is wasted.

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 usefully enumerates the returned fields and explains pagination. The analytics/plumbing parameters (context, llm_model, conversation_id) are left entirely to the schema, which is acceptable since their schema descriptions are detailed.

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 username, cursor and status filtering are fully documented in the schema already. The description only restates the username requirement and cursor usage, adding no new semantics such as status filter code meanings or default behavior.

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?

Names a specific verb and resource ("List a public MyAnimeList user's anime list") and clarifies the payload includes scores, tags and notes. It is distinguishable from myanimelist_user_manga_list_list by the anime-vs-manga resource, though the difference is only implicit in the resource name.

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?

The word "public" implies the precondition that only public profiles work, but there is no explicit when-to-use guidance, no statement of what happens for private lists, and no named alternative (e.g. the manga list tool or user_get). Usage context is implied rather than stated.

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