Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get MyAnimeList forum topic

myanimelist_forum_topic_get
Read-onlyIdempotent

Retrieve a MyAnimeList forum topic by numeric ID, including its posts and paging cursors so you can read discussions and continue through replies.

Instructions

Get a MyAnimeList forum topic with its posts and paging. 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_forum_topic_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. MyAnimeList numeric id.
cursorNoPass `page.nextCursor` from the previous response to get the next page.
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.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that the response includes the topic's posts and a paging mechanism, which is genuinely useful behavior beyond the annotations, but it says nothing about page size, ordering, or error conditions such as a missing or private topic.

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 with the core purpose front-loaded and no filler. The trailing 'Requires `id`' clause is largely redundant given the schema and slightly dilutes the useful payload information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a read-only, single-resource fetch whose annotations and fully described schema carry the safety and parameter burden. The description supplies the one thing an agent could not infer from structured fields, namely that posts and paging come back, so nothing essential is missing despite the absence of an output schema.

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 every parameter (including cursor, context, llm_model, conversation_id) is already documented. The description's only parameter note, 'Requires `id`', merely repeats the schema's required constraint and adds no new semantics, so the baseline of 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?

States a specific verb and resource ('Get a MyAnimeList forum topic') and adds the returned payload ('with its posts and paging'), which is more than a restatement of the name. It does not name or contrast any sibling such as myanimelist_club_get or the topic tools from other providers, so differentiation is left implicit.

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 the prerequisite 'Requires `id`', which the schema already enforces. There is no statement of when to use this versus a list/search-style sibling, no exclusions, and no note about when paging matters.

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