Skip to main content
Glama
cryptograss

MediaWiki MCP Server

by cryptograss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-recent-changes

Read-onlyIdempotent

Retrieve recent wiki change events, newest first, with filters for time, user, namespace, tags, and flags; paginate results to monitor edits, page creations, and log actions.

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

NameRequiredDescriptionDefault
tagNoChange tag — return only changes carrying this tag
userNoUsername — return only changes by this user. Mutually exclusive with excludeUser.
wikiNoWiki 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.
sinceNoISO 8601 timestamp — only return changes at or after this time
typesNoEvent types to include. Defaults to edit and new (content changes only).
untilNoISO 8601 timestamp — only return changes at or before this time
continueNoContinuation token from a prior call's truncation marker
hideAnonNoOmit edits by anonymous users
hideBotsNoOmit bot-flagged edits
hideMinorNoOmit minor-flagged edits
namespaceNoNamespace IDs to restrict the feed to — e.g. [0, 1] for main and talk
excludeUserNoUsername — exclude changes by this user. Mutually exclusive with user.
hidePatrolledNoOmit patrolled edits. Requires patrol rights.
hideRedirectsNoOmit changes whose target is a redirect
showPatrolStatusNoInclude per-row patrol status; adds an "Unpatrolled: yes" line to unpatrolled rows. Requires patrol rights.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.19.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds transparency by explaining pagination, filtering, boolean flag behavior, and patrol rights requirements, going beyond annotation-only information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph that is clear but could be more structured. It is front-loaded with the main purpose, but the length and density may reduce readability.

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 no output schema, the description explains row contents, filtering, pagination, and rights requirements. It is complete for the tool's complexity and provides necessary context for effective use.

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?

With 100% schema coverage, baseline is 3. The description adds meaning by explaining defaults for types, boolean flag behavior (appear only when true), mutual exclusivity of user/excludeUser, and the effect of showPatrolStatus.

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 the tool returns recent change events, newest first, in segments of 50. It specifies what each row includes and distinguishes from the sibling tool get-page-history 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 explains defaults, filtering options, and pagination. It explicitly directs users to get-page-history for single page history, providing clear context for when to use this tool vs alternatives.

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