Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Fandom Discussions threads

fandom_discussions_list
Read-onlyIdempotent

List Fandom wiki forum threads sorted by newest or trending, with cursor pagination and date/forum filters. Use it to monitor community discussions or find recent wiki topics.

Instructions

List Discussions forum threads on a Fandom wiki, newest or trending first. Requires wiki. Returns a list (use cursor 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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "fandom_discussions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage edition of the wiki, e.g. `de` for fortnite.fandom.com/de. Omit for the main (usually English) edition.
sortNo`newest` (by creation time) or `trending`. Default: `newest`.
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.
limitNoThreads per page, 1–100. Default: 25.
sinceNoOnly return items created at or after this ISO-8601 time, e.g. `2026-10-20T00:00:00Z`. Paging stops once older items are reached.
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.
forumIdNoOnly threads in this forum category (ids are in `forums`).
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 readOnly, idempotent, openWorld, and non-destructive, so safety is covered structurally. The description adds the ordering semantics ('newest or trending first') and the pagination hint, but says nothing about rate limits, result shape, or whether `since` truncates paging.

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 tight sentences with the scope, requirement, and pagination note front-loaded; nothing is wasted. The terseness, however, leaves no room for any usage or output context.

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 ten parameters and no output schema, the description should signal what a returned thread entry looks like and how pagination terminates, but it only mentions the cursor. The schema compensates fully for parameter meaning, so this is adequate but not complete.

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 ten parameters including sort enum, cursor, since, and limit are already documented; baseline 3 applies. The description only reinforces that `wiki` is required and that `cursor` drives paging, adding no meaning beyond the schema.

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 ('List Discussions forum threads on a Fandom wiki') plus the ordering options, which distinguishes it from the singular fandom_discussion_thread_get. It doesn't explicitly name that sibling or clarify whether thread post bodies are included, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Requires `wiki`' and 'use cursor when paginated' give minimal operational guidance. There is no statement of when to prefer this over the get-thread tool or over other fandom list tools, and no guidance on combining `sort`, `since`, and `forumId`.

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