Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList user reviews

myanimelist_user_reviews_list
Read-onlyIdempotent

Fetch a public MyAnimeList user's written reviews by username, returning a paginated list you can continue with a cursor.

Instructions

List the reviews written by a public MyAnimeList user. 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_reviews_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPass `page.nextCursor` from the previous response to get the next page.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds two useful non-annotation facts: only public members can be queried, and results may be paginated via cursor. It stops short of describing what a review record contains or whether an empty list means a private/nonexistent user.

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 scope, with no filler. The 'Requires `username`' sentence is mildly redundant against a schema that already marks it required with a pattern, which keeps it from a 5.

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

Completeness3/5

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

For a read-only list tool with no output schema, the description covers who and how to paginate but not what comes back or what an empty result means. Adequate to invoke correctly, but thin on return shape and privacy failure modes given there is no output schema to fall back on.

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 the baseline is 3 and every parameter (username pattern, cursor provenance, context, llm_model, conversation_id) is already documented in the schema. The description only restates that username is required and gestures at cursor pagination, adding no format or edge-case meaning beyond the schema.

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 names a specific verb plus resource plus scope: reviews written by a public MyAnimeList user. That distinguishes it in spirit from siblings like myanimelist_anime_reviews_list (reviews of a title) and myanimelist_user_anime_list_list (list entries), though no sibling is named explicitly to make the contrast airtight.

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?

Usage is only implied: it says the username is required and to use the cursor when paginated, which is invocation mechanics rather than when-to-use guidance. There is no statement of when to prefer this over the anime/manga review siblings or over myanimelist_user_get.

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