mediawiki-mcp-server

get-recent-changes

Read-onlyIdempotent

Retrieve recent changes from a MediaWiki wiki, filtered by type, namespace, user, or time window. Each row includes title, timestamp, user, size change, and flags.

Instructions

Returns recent change events, newest first, in segments of 50. Defaults to edits and page creations; set types to include log actions, categorizations, or external changes. Each row includes title, timestamp, user, revision IDs, size change, flags (minor/bot/new/anon), tags, and change type. Filter by timestamp window, namespaces, user, change tag, or hide flags (hideBots/hideMinor/hideAnon/hideRedirects/hidePatrolled). Pass showPatrolStatus to include per-row patrol state (requires patrol rights). Paginate with the continue token from the truncation marker. For a single page's revision history, use get-page-history. Boolean flags appear only when true; rows report the size delta, not raw old/new lengths.

Input Schema

TableJSON Schema

Name	Required	Description
`since`	No	ISO 8601 timestamp — only return changes at or after this time
`until`	No	ISO 8601 timestamp — only return changes at or before this time
`namespace`	No	Namespace IDs to restrict the feed to — e.g. [0, 1] for main and talk
`types`	No	Event types to include. Defaults to edit and new (content changes only).
`user`	No	Username — return only changes by this user. Mutually exclusive with excludeUser.
`excludeUser`	No	Username — exclude changes by this user. Mutually exclusive with user.
`tag`	No	Change tag — return only changes carrying this tag
`hideBots`	No	Omit bot-flagged edits
`hideMinor`	No	Omit minor-flagged edits
`hideAnon`	No	Omit edits by anonymous users
`hideRedirects`	No	Omit changes whose target is a redirect
`hidePatrolled`	No	Omit patrolled edits. Requires patrol rights.
`showPatrolStatus`	No	Include per-row patrol status; adds an "Unpatrolled: yes" line to unpatrolled rows. Requires patrol rights.
`continue`	No	Continuation token from a prior call's truncation marker
`wiki`	No	Wiki to target, as a key from the mcp://wikis/ resources (e.g. en.wikipedia.org), or the full mcp://wikis/ URI. Omit to use the default wiki.

Tool Definition Quality

A4.3/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds behavioral details: pagination with continue token, defaults to edit/new, boolean flags appear only when true, size delta reported, and patrol rights required for showPatrolStatus and hidePatrolled. No contradiction with annotations.

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?

The description is structured with main purpose first, then defaults, filters, pagination, sibling reference, and behavioral notes. Each sentence adds value without redundancy. Slight length is justified by the tool's complexity.

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?

Given 15 parameters and no output schema, the description covers pagination, defaults, special rights, and row content (title, timestamp, user, etc.). It lacks explanation of error conditions but is otherwise thorough and aids an agent in correct invocation.

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

Parameters4/5

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

Schema description coverage is 100%, providing baseline 3. The description adds context beyond schema: explanation of filter capabilities, pagination mechanism, special permission requirements, and the behavior of boolean flags (appearing only when true). This extra context justifies a higher score.

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?

The description clearly states 'Returns recent change events, newest first, in segments of 50,' specifying both verb and resource. It distinguishes from the sibling tool 'get-page-history' by noting its use for single page revision history.

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

Usage Guidelines4/5

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

The description provides guidance on default behavior, filter options, pagination, and when to use an alternative (get-page-history). It also mentions prerequisites like patrol rights for certain parameters. However, it does not explicitly state when not to use the tool beyond that.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ProfessionalWiki/MediaWiki-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server