Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get MyAnimeList anime title

myanimelist_anime_get
Read-onlyIdempotent

Retrieve MyAnimeList anime details by numeric ID, including information rows, statistics, synopsis, and related titles.

Instructions

Get a MyAnimeList anime title with its information rows, statistics, synopsis and related titles. 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_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.2/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's contribution is the content shape of the response (rows, stats, synopsis, related titles). It says nothing about invalid/unknown id handling, upstream rate limits, or whether statistics are a partial subset.

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?

Two sentences, front-loaded with what is fetched, no filler. The closing "Requires `id`" is marginally redundant given the schema's required array, but it is short and harmless.

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 must convey the return shape, and it does so by naming the four content sections. For a single-resource read that is close to sufficient; only error and edge-case behavior are unstated.

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%, including the numeric-range constraint on `id` and the instructions for context, llm_model and conversation_id. The only parameter text here is "Requires `id`", which repeats the schema's required list and adds no syntax, format or lookup guidance.

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 opens with a specific verb+resource ("Get a MyAnimeList anime title") and enumerates what the payload contains: information rows, statistics, synopsis, related titles. That distinguishes it from the manga and character siblings, but it does not address the overlap with myanimelist_anime_statistics_get, which the phrase "with its statistics" collides with.

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?

There is no when-to-use or when-not-to-use guidance and no named alternatives. The agent is told it needs an `id`, but nothing about preferring this over myanimelist_anime_statistics_get or the list endpoints for narrow information needs.

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