Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList anime recommendations

myanimelist_anime_recommendations_list
Read-onlyIdempotent

Retrieves recommended titles and user recommendations for a MyAnimeList anime using its numeric ID, helping you discover related shows and community suggestions.

Instructions

List the recommended titles and user recommendations for a MyAnimeList anime. Requires id. Returns a list.

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

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

C2.9/5.0
Behavior2/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 fully covered. Beyond that the description only adds 'Returns a list', which says nothing about pagination, result shape, or how the two recommendation types ('recommended titles' vs 'user recommendations') are distinguished in the response.

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 resource and scope, with no filler. The 'Requires `id`' sentence is mild redundancy against the required-fields schema but does not bloat the text.

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 simple read-only list tool with full annotation coverage, this is close to adequate. However, with no output schema, 'Returns a list' leaves the return structure unclear, particularly whether the two recommendation kinds come back as separate collections or combined.

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 metadata parameters (context, llm_model, conversation_id) that the description never mentions, so the schema carries the parameter burden. The description's 'Requires `id`' duplicates rather than enriches the schema, so baseline 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 gives a specific verb and resource: list recommended titles and user recommendations for a MyAnimeList anime. The 'anime' qualifier implicitly separates it from the manga counterpart, though it never names a sibling explicitly.

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 mention of alternatives such as myanimelist_manga_recommendations_list or myanimelist_anime_reviews_list. The only usage-adjacent statement is 'Requires `id`', which restates a schema constraint rather than advising the agent.

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