Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Fandom wiki activity

fandom_activity_list
Read-onlyIdempotent

Lists new posts on a Fandom wiki across discussions, article comments, and message walls so you can monitor community activity.

Instructions

List every new post on a Fandom wiki: Discussions, article comments and message walls. 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_activity_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage edition of the wiki, e.g. `de` for fortnite.fandom.com/de. Omit for the main (usually English) edition.
typeNoWhich posts to return. Default: `all`.
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.
limitNoPosts per page, 1–100. Default: 100.
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.
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

A3.6/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 fully covered. The description adds only the pagination/cursor behavior and the content-type scope; it says nothing about ordering, rate limits, or result size beyond 'a list'.

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, scope front-loaded, no filler. 'Requires `wiki`' mildly duplicates the schema's required list, which is the only waste.

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?

With 100% schema coverage, full annotations and no output schema, the description covers scope, the one non-obvious enum mapping, and pagination. The meta-parameters (context, llm_model, conversation_id) are fully documented in the schema, so nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 is the baseline, but the description adds real meaning by mapping the 'type' enum values to human terms ('Discussions, article comments and message walls' clarifies that `forum` means Discussions). It also flags `wiki` as required and names `cursor` as the paging mechanism.

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 every new post on a Fandom wiki') and enumerates the covered content types: Discussions, article comments and message walls. It does not name the narrower siblings (fandom_discussions_list, fandom_article_comments_list), so an agent must infer that this is the aggregate superset.

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 invocation prerequisites and a paging hint. There is no guidance on when to prefer this aggregate over the narrower siblings, and no exclusion for cases where the `type` filter would be better.

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