Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get MyAnimeList interest stack

myanimelist_stack_get
Read-onlyIdempotent

Retrieve a MyAnimeList interest stack by numeric ID, including its entries and restacks, to inspect stack contents and related social activity.

Instructions

Get a MyAnimeList interest stack with its entries and restacks. 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_stack_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 structurally. The description contributes the fact that the response embeds entries and restacks, which hints at payload depth, but says nothing about auth, rate limits, entry pagination, or the analytics parameters even though they are mandatory on every call.

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 short sentences, front-loaded with the action and resource, with zero filler. The trailing "Requires `id`" clause arguably does not earn its place since the schema already marks `id` as required.

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 single-id read with rich annotations, the description is adequate on purpose and payload composition, but with no output schema the agent still gets no sense of what a stack object looks like beyond "entries and restacks." A sentence on shape or ordering would close the gap.

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 (including the mandatory context, llm_model and conversation_id) are documented in the schema itself; baseline 3 applies. The description's only parameter statement, "Requires `id`," adds no meaning beyond the required array and the property description "Required. MyAnimeList numeric id."

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 interest stack") and adds what the payload contains (entries and restacks), which goes beyond restating the name. It does not distinguish itself from any alternative for retrieving the same resources, but the purpose itself is unambiguous.

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 "Requires `id`," which restates a schema requirement rather than saying when to use this tool. There is no indication of when a stack fetch is appropriate versus other anime/user endpoints, and no prerequisites or error conditions are described.

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