Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List MyAnimeList manga recommendations

myanimelist_manga_recommendations_list
Read-onlyIdempotent

Retrieve recommended titles and user recommendations for a MyAnimeList manga by its numeric ID to discover related reading options.

Instructions

List the recommended titles and user recommendations for a MyAnimeList manga. 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_manga_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. The description adds only 'Returns a list', which says nothing about pagination, result limits, entry shape, or whether the endpoint is public versus requiring auth — minimal value beyond the structured data.

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 with the required-parameter note up front and no redundant prose. 'Returns a list' is close to filler given it is self-evident from the tool name, but the definition is otherwise tight.

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 endpoint with full annotation and schema coverage, the definition is close to adequate, but with no output schema the agent still cannot tell what a recommendation entry contains or whether results are paginated. Those gaps are small but real.

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 all four parameters (id, context, llm_model, conversation_id) are documented in the schema itself. The description's 'Requires `id`' merely echoes that, so the baseline 3 applies — no added meaning, but no gap either.

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?

States a specific verb and resource: listing recommended titles and user recommendations for a MyAnimeList manga. The word 'manga' implicitly separates it from the sibling myanimelist_anime_recommendations_list, but the description never names that alternative or states the distinction 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. The only routing signal is the precondition 'Requires `id`', which restates the schema rather than telling the agent when this tool beats siblings like myanimelist_manga_reviews_list or myanimelist_manga_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