Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get MyAnimeList anime statistics

myanimelist_anime_statistics_get
Read-onlyIdempotent

Retrieve status counts and score histogram for a MyAnimeList anime by its numeric id to analyze how viewers rated and watched it.

Instructions

Get the status counts and score histogram for a MyAnimeList anime. Requires id.

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_statistics_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. MyAnimeList numeric id.
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.

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false) and open-world reach, so the description's remaining job is to say what comes back. It does describe the payload (status counts plus score histogram), which is valuable with no output schema, but says nothing about permissions, rate limits, or freshness of the statistics.

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 sentences, both earning their place: the first front-loads what the tool returns, the second carries the input prerequisite. No filler or redundant restatement of the title.

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?

For a simple read-only lookup with no output schema, the description sufficiently conveys the shape of the response and the required input, and the annotations handle safety. Minor gaps remain around what the histogram structure looks like and whether statistics reflect live or cached data.

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%, and every parameter including id, context, llm_model, and conversation_id is documented in the schema itself. The description only repeats that `id` is required, adding no new meaning, so the baseline of 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?

The description uses a specific verb ('Get') and names both the resource ('MyAnimeList anime') and the returned data ('status counts and score histogram'), which clearly separates it from the detail-oriented sibling myanimelist_anime_get. It stops short of explicitly naming that sibling, so differentiation is inferred rather than stated.

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?

The only guidance is the prerequisite 'Requires `id`', which restates the required schema field rather than explaining when this tool is the right choice. There is no mention of when not to use it or of alternatives such as myanimelist_anime_get for general anime details.

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