Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Fandom wiki page

fandom_page_get
Read-onlyIdempotent

Retrieve a Fandom wiki article's text, wikitext, infoboxes, and metadata using the wiki subdomain and page title to support research, content extraction, or coding tasks.

Instructions

Get a Fandom wiki article's text, wikitext, infoboxes and metadata. Requires wiki and title.

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_page_get"
  }
}

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.
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.
includeHtmlNoAlso return the rendered article HTML. Default: false.
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.
includeWikitextNoReturn the page's wikitext source. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds useful return-shape context by naming the four content blocks returned. It says nothing about rate limits, redirects/404 behavior, or the stateful conversation_id handshake described in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and return payload, with zero filler. Nothing is repeated or padded.

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 8-parameter tool with no output schema, the description is thin: it lists returned content but omits that context and llm_model are also required, stating only that wiki and title are required — a potentially misleading omission that could cause a validation error. The conversation_id sequencing rule is left entirely to the schema.

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 lang, includeHtml, includeWikitext, context and conversation_id is already documented in the schema. The description only restates that wiki and title are required and adds no format or syntax detail beyond that. Baseline 3 applies when the schema does the heavy lifting.

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 ('Get a Fandom wiki article') and enumerates the payload (text, wikitext, infoboxes, metadata), which tells an agent what comes back. It does not differentiate from close siblings such as fandom_wiki_get or wikipedia_page_get, so the 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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. Given siblings like fandom_wiki_get, fandom_search_list and wikipedia_page_get, an agent gets no routing signal for choosing this tool over them. Only a bare prerequisite ('Requires `wiki` and `title`') is offered.

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