Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Wikipedia page revisions

wikipedia_page_revisions_list
Read-onlyIdempotent

Retrieve a Wikipedia page's revision history, including editors, byte sizes, tags, and date windows, to track changes or investigate edits. Use cursors for paginated results.

Instructions

List a Wikipedia page's revisions with users, sizes and tags; a reversed date window is swapped for the chosen direction. 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_page_revisions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the window as a real `YYYY-MM-DD` day (read as midnight UTC) or a full ISO 8601 date-time with a zone.
dirNoDirection from `from`: `older` (default) or `newer`. A reversed `from`/`to` window is swapped for the chosen direction.older
fromNoStart of the window as a real `YYYY-MM-DD` day (read as midnight UTC) or a full ISO 8601 date-time with a zone.
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
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
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds useful behavioral context beyond those annotations: it discloses returned fields, pagination via cursor, and the rule that a reversed date window is swapped according to `dir`. It does not mention rate limits or auth requirements, but those are not central for this read-only listing tool.

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?

The description is compact and front-loaded: it begins with the core action and resource, then adds return fields and the key date-window rule. Every sentence contributes practical information without unnecessary repetition.

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 ten-parameter listing tool with no output schema, the description covers the required title, returned fields, pagination, and directional date-window behavior. It does not describe the full response shape or provide alternative-selection guidance, but the schema covers the parameters thoroughly and the description is sufficient to call the tool correctly.

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 the schema already documents all ten parameters in detail. The description adds only a reminder that `title` is required and that the cursor is used for pagination, both of which are already present in the schema. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 a Wikipedia page's revisions. It also names the returned fields (users, sizes, tags), making the purpose concrete. It does not explicitly differentiate from sibling tools such as page history stats or recent changes, so it falls 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 Guidelines2/5

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

The description only states that `title` is required and that the cursor should be used when paginated. It gives no guidance on when to choose this tool over alternatives like `wikipedia_page_history_stats_get` or `wikipedia_recent_changes_list`, and no when-not conditions are provided.

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