Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Fandom recent changes

fandom_recent_changes_list
Read-onlyIdempotent

Fetches recent edits, new pages, and log events from a Fandom wiki to track changes and monitor activity. Supports filtering by type, time, and namespace.

Instructions

List recent edits, new pages and log events on a Fandom wiki. 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_recent_changes_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage edition of the wiki, e.g. `de` for fortnite.fandom.com/de. Omit for the main (usually English) edition.
typeNo`edit`, `new` (page creations), `log` (moves, uploads, blocks…) or `all`. 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.
limitNoChanges per page, 1–500. Default: 100.
sinceNoOnly changes at or after this ISO-8601 time. Fandom keeps about 90 days.
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.
namespaceNoOnly this namespace (0 = articles). Default: all namespaces.
includeBotsNoInclude bot edits. Default: true.
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 fully covered without the description. The description adds two behavioral facts beyond that — it returns a list and pagination is cursor-based — but says nothing about result volume, ordering, or the ~90-day retention window that constrains results.

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 purpose, then the prerequisite, then the return/pagination note. Nothing is padded. 'Requires `wiki`' mildly duplicates the schema's required list, keeping it just below a 5.

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?

For an 11-parameter, 3-required tool with no output schema, the description is thin but not broken: schema coverage is complete and annotations carry the safety semantics. Still, it omits the meaningful constraints an agent would want stated up front (the ~90-day `since` window, default limit of 100, default includeBots=true) and gives no shape for the returned list beyond 'a list'.

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 (wiki format, type enum, limit, since, cursor, namespace, includeBots) is already documented in the schema. The description only reiterates that `wiki` is required and points at the cursor field, adding no meaning beyond the schema. Baseline 3 is appropriate.

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?

The description gives a specific verb and resource set: 'List recent edits, new pages and log events on a Fandom wiki.' An agent can immediately tell this is a feed-of-changes tool scoped to a single wiki. It does not name or contrast with nearby siblings such as fandom_activity_list, so it falls 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?

It states a hard prerequisite ('Requires `wiki`') and gives a pagination instruction ('use cursor when paginated'), which is genuine usage guidance. However, it never says when to prefer this over fandom_activity_list or wikipedia_recent_changes_list, nor any when-not conditions, so the routing guidance is only implied.

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