Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get MyAnimeList manga title

myanimelist_manga_get
Read-onlyIdempotent

Retrieve a MyAnimeList manga by numeric ID to access its information rows, statistics, synopsis, and related titles.

Instructions

Get a MyAnimeList manga 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_manga_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=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered upstream. The description adds only the content inventory of the response — useful since there is no output schema — but says nothing about 404 behavior for invalid ids, rate limiting, or whether the included statistics block duplicates a separate endpoint.

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 the resource and outcome, with zero filler. Slightly terse in the second sentence but nothing is wasted.

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 read-only single-record fetch with no output schema, listing the returned sections partially compensates for the absent return documentation, and annotations cover the safety side. It remains incomplete on error/not-found handling and on the meta-parameters (context, llm_model, conversation_id) that the schema requires on every call.

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 all four parameters (id, context, llm_model, conversation_id) are already documented, and the description's "Requires `id`" merely restates the required field. It adds no constraint or format detail beyond the schema; a baseline 3 is appropriate.

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 ("Get a MyAnimeList manga title") and enumerates the payload the agent receives (information rows, statistics, synopsis, related titles). That is enough to distinguish it from the manga_*_list siblings, though it never names which sibling to prefer when the agent only wants, say, statistics or characters.

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?

"Requires `id`" is a precondition, not usage guidance. There is no statement of when to pick this tool over myanimelist_manga_statistics_get, myanimelist_manga_characters_list, or the user-list sibling, and no exclusion such as "for a full title record only, not for browsing."

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