Skip to main content
Glama
olgasafonova

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_get_recent_changes

Read-only

Retrieve recent edits, new pages, and log events across a MediaWiki. Filter by timestamp, namespace, or change type, and group results by user, page, or type.

Instructions

Get recent changes across the entire wiki.

USE WHEN: User asks "what's been changed recently", "show wiki activity", "who's been editing".

NOT FOR: Single page history (use mediawiki_get_revisions). Not for user-specific edits (use mediawiki_get_user_contributions).

PARAMETERS:

  • limit: Max changes (default 50)

  • start, end: Time range (ISO 8601)

  • namespace: Filter by namespace

  • type: Filter by change type (edit, new, log)

  • aggregate_by: Group results - "user", "page", or "type"

RETURNS: Recent changes with timestamps, users, and summaries. Aggregation returns counts.

Input Schema

NameRequiredDescriptionDefault
endNoUpper time bound (ISO 8601). Returns changes on or before this timestamp.
typeNoFilter by type: 'edit', 'new', 'log', or empty for all
limitNoMaximum changes to return (default 50, max 500)
startNoLower time bound (ISO 8601). Returns changes 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.
aggregate_byNoAggregate results by: 'user', 'page', or 'type'. Returns counts instead of raw changes. Recommended for large result sets.
continue_fromNoContinue token for pagination

Output Schema

NameRequiredDescriptionDefault
changesNo
has_moreYes
aggregatedNo
continue_fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.32.0
    • changedInput schema / properties / end / description
      Previous value: -"End timestamp (ISO 8601)"New value: +"Upper time bound (ISO 8601). Returns changes on or before this timestamp."
    • changedInput schema / properties / start / description
      Previous value: -"Start timestamp (ISO 8601)"New value: +"Lower time bound (ISO 8601). Returns changes 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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: aggregate_by changes the return type to counts instead of raw changes, and the RETURNS section describes the shape (timestamps, users, summaries). It stops short of auth, rate-limit or pagination-behavior disclosure, hence a 4 rather than 5.

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 purpose, then structured USE WHEN / NOT FOR / PARAMETERS / RETURNS sections. Every sentence earns its place and the routing information comes before the parameter recap.

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?

For an 8-parameter read tool with an output schema present, all the agent needs is here: purpose, triggers, alternatives and filter semantics. Return values are additionally summarized even though the output schema already carries them.

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 is already documented in the schema, including defaults, ISO 8601 format and the aggregate_by recommendation. The description largely restates those same parameters without adding syntax or constraints beyond the schema, so 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 and resource ('Get recent changes across the entire wiki') with explicit scope. It names the sibling tools it is NOT for (mediawiki_get_revisions, mediawiki_get_user_contributions), so an agent can disambiguate 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 triggers ('what's been changed recently', 'wiki activity', 'who's been editing') and a NOT FOR section routing to the two correct alternatives. Nothing about when to select this tool 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