Skip to main content
Glama
olgasafonova

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_get_user_contributions

Read-only

Retrieve all edits made by a specific wiki user with timestamps and summaries; filter by date range, result limit, or namespace.

Instructions

Get all edits made by a specific user.

USE WHEN: User asks "what did John edit", "show user's contributions", "list edits by admin".

NOT FOR: Page-specific history (use mediawiki_get_revisions). Not for wiki-wide activity (use mediawiki_get_recent_changes).

PARAMETERS:

  • user: Username (required)

  • limit: Max contributions (default 50)

  • start, end: Time range (ISO 8601)

  • namespace: Filter by namespace

RETURNS: List of pages edited with timestamps and summaries.

Input Schema

NameRequiredDescriptionDefault
endNoUpper time bound (ISO 8601). Returns contributions on or before this timestamp.
userYesUsername to get contributions for
limitNoMax contributions to return (default 50, max 500)
startNoLower time bound (ISO 8601). Returns contributions on or after this timestamp.
namespaceNoFilter by namespace (-1 for all)
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.

Output Schema

NameRequiredDescriptionDefault
userYes
countYes
has_moreYes
contributionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.32.0
    • changedInput schema / properties / end / description
      Previous value: -"End at this timestamp (ISO 8601)"New value: +"Upper time bound (ISO 8601). Returns contributions on or before this timestamp."
    • changedInput schema / properties / start / description
      Previous value: -"Start from this timestamp (ISO 8601, newer first)"New value: +"Lower time bound (ISO 8601). Returns contributions on or after this timestamp."
  2. Changed1 schema field changedv1.31.0
    • addedInput schema / properties / rationale
      Added value: +{
+  "description": "Optional one-sentence explanation of why you are calling this tool. Used for audit trails when present.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint=false, so the safety profile is covered structurally. The description adds a RETURNS line and parameter behavior, but since an output schema exists that return summary is largely redundant and the description adds little behavioral context beyond annotations. Adequate, not rich.

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?

Front-loaded with the core verb, then clearly labeled USE WHEN / NOT FOR / PARAMETERS / RETURNS sections. No filler sentences; every line carries routing or parameter information.

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?

With annotations covering safety, a full input schema, and an output schema handling return values, the description supplies everything else needed: purpose, routing, parameter summary. Nothing an agent needs to invoke correctly is missing.

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 start/end semantics and the namespace=-1 sentinel is already documented in the schema. The description restates the params (and omits the rationale param) without adding format or edge-case 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('all edits made by a specific user'), and explicitly scopes itself against mediawiki_get_revisions and mediawiki_get_recent_changes. An agent can select it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides explicit USE WHEN trigger phrases and an explicit NOT FOR clause naming the two alternative tools for the confusable cases. This is textbook when/when-not/alternatives routing.

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