Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Wikipedia recent changes

wikipedia_recent_changes_list
Read-onlyIdempotent

List and filter recent changes on a Wikipedia edition by type, namespace, page, or time to monitor edits, new pages, and logs; paginate with a cursor.

Instructions

List recent changes on a Wikipedia edition by type, namespace, page or time. Optional inputs: lang, type, namespace, since, title and 2 more. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_recent_changes_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
typeNoOnly changes of this type.
limitNoRows per page, 1 to 500. Default: 50.
sinceNoOnly changes at or after this time, as `YYYY-MM-DD` or an ISO 8601 date-time with a zone.
titleNoOnly changes to this page.
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.
namespaceNoNamespace id, e.g. `0` for articles or `14` for categories.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description only adds the fact that it returns a list and that a cursor is used when paginated, which is useful but thin given the annotations carry the rest.

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?

Two compact sentences with the resource and scope front-loaded and zero wasted prose. The vague '2 more' phrasing is the only minor inefficiency.

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 paginated list tool with a fully documented schema and no output schema, the description plus annotations give an agent enough to call it correctly, including the cursor caveat. A note on ordering or default result size would make it complete.

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 enum, namespace, since, title and cursor is already documented in the schema. The description merely names a few filters and says '2 more' without adding format or interaction meaning, so 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?

States a specific verb and resource ('List recent changes on a Wikipedia edition') and enumerates the filter dimensions (type, namespace, page, time), which lets an agent distinguish it from sibling history tools like wikipedia_page_revisions_list or wikipedia_logs_list. It stops short of naming an alternative explicitly.

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?

Usage is implied by the filter list and the pagination note, so an agent can infer it is for broad, filterable change feeds. However, there is no explicit when-to-use versus when-not guidance pointing at the sibling tools that also return change or history data.

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