Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Wikipedia category members

wikipedia_category_members_list
Read-onlyIdempotent

List Wikipedia category members with sort keys, timestamps, and category counts, then paginate by cursor to inspect pages, subcategories, or files.

Instructions

List a Wikipedia category's members with sort keys and timestamps, plus the category counts. Requires title. 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": {
      "title": "<title>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_category_members_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
sortNoSort by `sortkey` (default) or by the time the member joined.sortkey
typeNoOnly members of this kind: `page`, `subcat` or `file`.
limitNoRows per page, 1 to 500. Default: 50.
titleYesRequired. Page title on the chosen edition, e.g. `Albert Einstein`, `C++` or `Talk:Barack Obama`. URL-encode it in the path.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
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.
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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety and repeatability are covered. The description adds genuine value beyond that by stating the response carries sort keys, timestamps and category counts and that pagination uses a cursor, but it says nothing about the 'category counts' field's meaning, missing-category behavior, or continuation limits.

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 what the tool returns, with no filler. 'Requires `title`' is mildly redundant with the schema's required list and its own description, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only paginated listing tool, the description covers the resource, the required input, the notable return fields, and the pagination mechanism. The remaining parameters (context, llm_model, conversation_id, lang, sort, type, limit) are fully documented in the schema, and with no output schema the brief note on returned fields is proportionate.

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%, including enums for `sort` and `type` and defaults for `lang`, `sort` and `limit`, so the schema carries the parameter burden. The description only restates that `title` is required and that the cursor applies to pagination, adding no new parameter meaning.

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 names a specific verb and resource ('List a Wikipedia category's members') and enumerates what comes back (sort keys, timestamps, category counts), which is enough to distinguish it from the page-level siblings like wikipedia_page_links_list or wikipedia_search_list. It stops short of explicitly naming any sibling as an alternative, so it is clear but not differentiated by contrast.

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 gives two practical constraints: `title` is required, and the cursor is for paginated follow-ups. There is no explicit when-to-use / when-not-to-use guidance and no routing to alternatives such as search or page-links tools when the agent actually wants member content rather than membership listings.

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