Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList anime reviews

myanimelist_anime_reviews_list
Read-onlyIdempotent

Fetch paginated MyAnimeList anime reviews with ratings, reactions, tags and full text by anime ID. Sort by suggested, newest or mostvoted and optionally include spoilers or preliminary reviews.

Instructions

List MyAnimeList anime reviews with ratings, reactions, tags and full text. Requires id. 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": {
      "id": "<id>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "myanimelist_anime_reviews_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. MyAnimeList numeric id.
sortNoReview order: `suggested` (default), `newest` or `mostvoted`.
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.
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.
includeSpoilersNoInclude spoiler-tagged reviews. Default: false.
includePreliminaryNoInclude preliminary reviews. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/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 safety profile is covered. The description adds value the annotations lack: the shape of returned content (ratings, reactions, tags, full text) and the pagination contract ('use cursor when paginated'), which matters since there is no output schema.

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?

Two tight sentences with zero filler; the payload description and the required-param/pagination constraints are front-loaded. Every clause earns its place.

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 8 parameters and no output schema, the description compensates by naming the returned fields and explaining cursor-based paging, which is what an agent needs to interpret the response. It stops short of noting default filters (includeSpoilers/includePreliminary) that affect result content, a minor residual gap.

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 schema already documents id, sort, cursor, includeSpoilers, and includePremium fields. The description only restates that id is required and points at cursor without adding format or default details. Baseline 3 is appropriate when the schema does the heavy lifting.

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 uses a specific verb+resource ('List MyAnimeList anime reviews') and enumerates the returned payload (ratings, reactions, tags, full text), so an agent knows exactly what it retrieves. It does not name any sibling (e.g. manga_reviews_list or user_reviews_list) to disambiguate, though 'anime' vs 'manga' offers partial separation by resource.

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?

'Requires `id`' and 'use cursor when paginated' are useful prerequisites and mechanics, implying the tool is for fetching reviews of a known anime. However, there is no explicit guidance on when to choose this over manga_reviews_list or user_reviews_list, and no note on when spoiler/preliminary reviews should be included.

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