Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Fandom wiki pages

fandom_pages_list
Read-onlyIdempotent

List every page on a Fandom wiki in title order, with optional prefix, namespace, and redirect filters; paginate using a cursor to retrieve large wikis page by page.

Instructions

List every page on a Fandom wiki in title order. 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_pages_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage edition of the wiki, e.g. `de` for fortnite.fandom.com/de. Omit for the main (usually English) edition.
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.
limitNoItems per page, 1–500. Default: 100.
cursorNoPass `page.nextCursor` from the previous response to get the next page.
prefixNoOnly titles starting with this text.
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.
namespaceNoMediaWiki namespace number. 0 = articles (default), 14 = categories, 6 = files, 2 = user pages.
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.
includeRedirectsNoInclude redirect pages. Default: false. Fandom drops redirects after counting `limit`, so a page can hold fewer items while `hasMore` is still true.

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, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the title-ordering guarantee and a pagination/cursor note, but says nothing about result size behavior, redirect handling, or what the returned list contains.

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 with the core action and scope front-loaded, and no filler. "Requires `wiki`" is mildly redundant with the schema's required list, but it is a cheap, useful reinforcement rather than waste.

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 a 10-parameter, open-world enumeration tool with no output schema, the description is thin: it gestures at the return value ("Returns a list") but omits the namespace/prefix filtering story and the redirect quirk documented only in the schema. It is adequate to call the tool, but not complete for a tool of this complexity.

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 (lang, prefix, namespace, limit, includeRedirects, cursor, context, llm_model) is already documented in the schema. The description only echoes that `wiki` is required and that `cursor` drives pagination, adding no syntax or format 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?

The description states a specific verb and resource ("List every page on a Fandom wiki") plus an ordering guarantee ("in title order"), which is more than the title alone. It does not, however, distinguish this from siblings such as fandom_search_list or fandom_category_members_list, so an agent must infer the boundary itself.

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 usage guidance is "use cursor when paginated," which is a mechanical hint rather than a when-to-use rule. There is no statement of when to prefer this enumeration over fandom_search_list or fandom_category_members_list, and no exclusions or prerequisites beyond the bare "Requires `wiki`."

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