Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Fandom Discussions thread

fandom_discussion_thread_get
Read-onlyIdempotent

Retrieves a Fandom Discussions thread and its replies by wiki and thread ID, with pagination, optional language selection, and reply sorting.

Instructions

Get a Fandom Discussions thread and its replies. Requires wiki and threadId.

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": {
      "wiki": "<wiki>",
      "threadId": "<threadId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "fandom_discussion_thread_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage edition of the wiki, e.g. `de` for fortnite.fandom.com/de. Omit for the main (usually English) edition.
sortNoReply order. `newest` (default) pages through every reply with `cursor`. `oldest` returns the first `limit` replies only, without further pages.
wikiYesFandom wiki subdomain, e.g. `fortnite` for fortnite.fandom.com or `blox-fruits` for blox-fruits.fandom.com. A full wiki host or URL is also accepted.
limitNoReplies per page, 1–100. Default: 100.
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.
threadIdYesDiscussions thread id, e.g. `4400000000000172871` (from a thread URL `/f/p/<id>`).
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 safety is covered. The description adds only that replies come back with the thread, which is useful scope context but thin beyond that — no note on pagination behavior or auth needs.

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 resource and its scope of return. No filler, though the second sentence is pure schema restatement and could have carried more value.

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?

With nine parameters (four required), no output schema, and multi-page replies, the description is minimal — it never mentions reply ordering or cursor paging, which the schema does cover, but it also does not describe the returned shape 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% and every parameter carries detailed docs (including sort semantics and cursor paging), so the schema does the heavy lifting. The description's 'Requires wiki and threadId' merely restates requiredness without adding meaning, which matches the baseline 3 when coverage is high.

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?

Names a specific verb and resource: getting a single Fandom Discussions thread plus its replies. That distinguishes it in spirit from the list siblings, though no sibling is named explicitly, so the differentiation relies on the agent inferring singular vs list.

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 description only states required parameters (wiki, threadId) — a prerequisite, not usage guidance. It gives no when-to-use condition, no exclusion against fandom_discussions_list or other thread-reading paths, and no note on when to page via cursor.

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