Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Fandom wiki

fandom_search_list
Read-onlyIdempotent

Search a Fandom wiki's pages by keyword to find relevant articles, categories, or files. Returns a paginated list of matching results.

Instructions

Search the pages of a Fandom wiki by keyword. Requires wiki and query. Returns a list (use page 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>",
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "fandom_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage edition of the wiki, e.g. `de` for fortnite.fandom.com/de. Omit for the main (usually English) edition.
pageNoPage number (1-based). Default: 1.
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.
limitNoResults per page, 1–100. Default: 25.
queryYesRequired. Search 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.

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, openWorldHint and non-destructive, so the safety profile is fully covered structurally. The description's contribution is the return shape ('Returns a list') and the existence of pagination, which matters because there is no output schema. It says nothing about result ordering, rate limits, or wiki-existence failures.

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?

Three short sentences, front-loaded with the action and resource, then requirements, then return shape. No filler or redundancy.

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?

For a read-only open-world search with a fully documented 9-parameter schema and no output schema, the description covers action, required inputs, and return shape. The only real gap is the absence of routing guidance against the several sibling search/list tools.

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 coverage is 100%, including detailed descriptions for wiki, lang, namespace, and limit, so the schema carries the parameter burden. The description only repeats that wiki and query are required, adding no syntax or format insight 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?

States a specific verb and resource ('Search the pages of a Fandom wiki by keyword') and names the two required inputs, so the agent knows exactly what the tool does. It does not differentiate against close siblings such as fandom_pages_list or fandom_wiki_get, which keeps it from 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 Guidelines2/5

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

The only guidance is the parenthetical 'use page when paginated', which points at a parameter rather than at an alternative tool. There is no statement of when to prefer this over fandom_pages_list or fandom_wiki_get, and no preconditions beyond the trivially restated required params.

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