Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Wikipedia user contributions

wikipedia_user_contributions_list
Read-onlyIdempotent

List a Wikipedia user's contributions, including edit sizes, comments, tags, and flags, with optional language, namespace, date, and pagination filters.

Instructions

List a Wikipedia user's contributions with sizes, comments, tags and flags. Requires name. 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": {
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_user_contributions_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.
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
nameYesRequired. User name on the edition, e.g. `Jimbo Wales` or `ClueBot NG`. A profile URL is not accepted. An IP address has no user record; use the contributions route for its edits.
limitNoRows per page, 1 to 500. Default: 50.
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

B3.2/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 the safety profile is covered. The description adds useful context about the shape of the result (a list carrying sizes, comments, tags and flags) and that results may be paginated via a cursor. It does not mention rate limits, ordering, or whether anonymous/IP contributors are included.

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, front-loaded sentences with no padding and the required-parameter caveat placed early. The 'Requires `name`' clause is slightly redundant against a schema that already marks it required, which keeps it off a 5.

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

Completeness3/5

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

With 10 parameters (including date-window, namespace and conversation-tracking params) and no output schema, the description is thin: it never mentions that results can be scoped by date range or namespace, which are the main filtering dimensions an agent would need. It does cover the required name and pagination behavior, so it is adequate but with clear gaps.

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 limit, cursor, namespace, from and to is already documented in the schema — the baseline of 3 applies. The description adds nothing beyond the schema; 'Requires `name`' and the cursor note simply echo what the schema states more fully.

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?

A specific verb plus resource ('List a Wikipedia user's contributions') and it names the fields returned (sizes, comments, tags, flags), so it is clearly not a profile fetch or a page-revision list. It stops short of naming the sibling it differs from (e.g. wikipedia_user_get), so it is clear but not differentiated.

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 procedural guidance is 'Requires `name`' and 'use cursor when paginated', both of which restate the schema. There is no statement of when to prefer this over wikipedia_user_get or wikipedia_page_revisions_list, nor any exclusion or prerequisite beyond the required parameter.

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