Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Fandom article comments

fandom_article_comments_list
Read-onlyIdempotent

Retrieve comments and replies from a Fandom wiki article by providing the wiki subdomain and page title, with pagination support for long discussion threads.

Instructions

List the comments and replies under a Fandom wiki article. Requires wiki and title. Returns a list (use page when paginated).

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>",
      "title": "<title>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "fandom_article_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage edition of the wiki, e.g. `de` for fortnite.fandom.com/de. Omit for the main (usually English) edition.
pageNoPage number (1-based). Default: 1.
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.
titleYesPage title as it appears in the wiki URL, e.g. `Peely` or `Chapter_7:_Season_4`. Spaces and underscores are equivalent. A full page URL is also accepted, and a `#section` is ignored.
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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only that output is a list and that the `page` parameter handles pagination, which is thin but not contradictory; nothing is said about ordering, threading depth, or result limits.

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, front-loaded with the action and resource, then requirements, then return shape. No filler, though the 'use page when paginated' clause is slightly circular.

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

Completeness4/5

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

For a read-only list tool with full schema coverage and no output schema, the description covers purpose, required inputs, and return shape adequately. It could say more about comment threading or pagination limits, but nothing essential to invoking it is missing.

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 `wiki`, `title`, `lang`, and `page` is already documented in the schema. The description merely restates the two required fields and echoes the pagination behavior, adding no new semantics.

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 ('List') and resource ('comments and replies under a Fandom wiki article'), which clearly separates it from retrieval siblings like fandom_page_get. It does not, however, distinguish itself from near-neighbors such as fandom_discussions_list or fandom_discussion_thread_get.

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 a prerequisite ('Requires `wiki` and `title`') plus a passing pagination hint. There is no statement of when to prefer this over the discussions or thread tools, and no exclusions.

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