mediawiki-mcp-server

get-recent-changes

Read-onlyIdempotent

Retrieve recent changes from a MediaWiki wiki, filtered by type, time, user, namespace, or tag. Returns newest-first segments of 50 events with details like title, user, revision IDs, and flags. Use continue token to paginate.

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.

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

Tool Definition Quality

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. The description adds significant behavioral context beyond annotations, including segment size, default event types, returned fields, filtering details, and patrol rights requirements, without any contradictions.

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 a dense, coherent paragraph with all necessary information front-loaded. Every sentence adds value, though it could be slightly more structured (e.g., breaking into sections) for improved readability.

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?

Given the complexity (14 parameters, no output schema), the description is thorough. It covers parameter behavior, defaults, pagination, filtering, auth requirements, and return fields. An agent has sufficient information to use the tool correctly.

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%, so baseline is 3. The description adds meaning beyond the schema by explaining defaults, grouping filters, and providing context like 'requires patrol rights' for hidePatrolled and showPatrolStatus. This justifies a 4.

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 that the tool returns recent change events, newest first, in segments of 50. It also explicitly distinguishes itself from the sibling tool get-page-history, making its purpose unambiguous.

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?

The description provides explicit guidance on when to use this tool vs alternatives (e.g., 'For a single page's revision history, use get-page-history'). It also explains default behavior, filtering options, pagination, and authentication requirements for patrol features.

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