Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Fandom category members

fandom_category_members_list
Read-onlyIdempotent

List pages, subcategories, and files in a Fandom wiki category to explore or audit category contents, with pagination support for large results.

Instructions

List the pages, subcategories and files in a Fandom wiki category. Requires wiki and category. 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>",
      "category": "<category>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "fandom_category_members_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 members 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.
limitNoItems per page, 1–500. Default: 100.
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.
categoryYesCategory name, with or without the `Category:` prefix, e.g. `Outfits`.
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?

The annotations already declare this a safe, read-only, idempotent, open-world listing, so the safety profile is covered. The description adds the pagination behavior (cursor-based continuation) and the three member kinds returned, but says nothing about ordering, page size defaults, or rate/limit behavior beyond 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?

Three short sentences that are front-loaded with the purpose, followed by requirements and the return/pagination behavior. No filler, no repetition of the title, and every sentence carries distinct information.

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 no output schema, the description does state the return shape at a high level (a list, paginated via cursor), which is the key missing piece. It could go further by describing what a member entry contains, but for a straightforward read-only listing over a fully documented 9-parameter schema, it is largely sufficient.

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, type, limit, and cursor is already documented with examples and defaults. The description only restates that wiki and category are required and hints at cursor usage, adding no meaning beyond the schema; baseline 3 applies.

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 the pages, subcategories and files in a Fandom wiki category'), which is far more informative than the name alone and tells the agent the member kinds returned. It does not explicitly distinguish itself from nearby siblings such as fandom_pages_list or kick_category_get, so it stops 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 notes the two key prerequisites (wiki and category) and gives one piece of operational guidance ('use cursor when paginated'), which is useful context for iteration. However, there is no explicit when-to-use versus alternatives guidance, and the required-parameter note largely repeats the schema's required list.

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