Skip to main content
Glama
olgasafonova

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_get_revisions

Read-only

Retrieve a wiki page's revision history to see who edited it, when, and what summaries were left. Filter by user or date range and get timestamps, sizes, and edit notes.

Instructions

Get revision history for a specific page.

USE WHEN: User asks "who edited the FAQ", "show edit history of X", "when was this page last changed".

NOT FOR: Wiki-wide activity (use mediawiki_get_recent_changes). Not for comparing versions (use mediawiki_compare_revisions).

PARAMETERS:

  • title: Page name (required)

  • limit: Max revisions (default 50)

  • start, end: Time range (ISO 8601)

  • user: Filter by user

RETURNS: Revision list with timestamps, users, sizes, and edit summaries.

Input Schema

NameRequiredDescriptionDefault
endNoUpper time bound (ISO 8601). Returns revisions on or before this timestamp.
userNoFilter to revisions by this user
limitNoMax revisions to return (default 20, max 100)
startNoLower time bound (ISO 8601). Returns revisions on or after this timestamp.
titleYesPage title to get revision history for
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.

Output Schema

NameRequiredDescriptionDefault
countYes
titleYes
page_idYes
has_moreYes
revisionsYes

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 revisions 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 revisions 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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=false, so safety and side-effect profile are covered. The description adds the return payload shape (timestamps, users, sizes, edit summaries), which is useful but duplicated by the output schema, and it says nothing about pagination behavior or the query cost of wide time ranges. Adequate but not rich beyond the structured fields.

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 one-line purpose followed by tight USE WHEN / NOT FOR / PARAMETERS / RETURNS blocks. Every line earns its place and the routing rules appear before the parameter list.

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?

Output schema exists (so return values needn't be re-explained), all six parameters are schema-documented, the sole required parameter is clear, and the when/when-not routing is explicit. An agent has everything needed to select and call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline would be 3, but the description actively contradicts the schema: it states 'limit: Max revisions (default 50)' while the schema says default 20, max 100. Misstating a default can cause an agent to size requests incorrectly, which is worse than saying nothing.

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 + resource + scope: 'Get revision history for a specific page.' It explicitly names the siblings it must not be confused with (mediawiki_get_recent_changes, mediawiki_compare_revisions), so an agent can discriminate 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 concrete trigger phrases under USE WHEN ('who edited the FAQ', 'show edit history of X', 'when was this page last changed') and explicit exclusions under NOT FOR with the correct alternative tool for each case. Nothing is left to inference.

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