Skip to main content
Glama

get-recent-changes

Read-onlyIdempotent

Fetch recent wiki changes with filters for time, user, namespace, and event type. Each result includes title, timestamp, user, size change, flags, and more.

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

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

Discloses pagination (50 per segment, continue token), default types, filtering options, and rights requirements. Annotations already indicate readOnly and idempotent, but description adds valuable behavioral context beyond 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?

Single paragraph that covers all key points without redundancy. Could be improved by breaking into bullet points for readability, but it is clear and efficient.

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 the tool's complexity (14 parameters, no output schema), the description covers purpose, pagination, filtering, rights, and differentiation. It lists output fields but misses the exact response structure, which is acceptable without output schema.

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?

All 14 parameters have schema descriptions (100% coverage). The description adds context: defaults for types, explanation of hide flags, and patrol status behavior. While schema covers basics, description clarifies compound semantics like mutually exclusive user parameters.

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 it returns recent change events, newest first, in segments of 50. It lists fields included and differentiates from the sibling tool get-page-history for a single page's 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 Guidelines5/5

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

Explicitly states defaults (edits and page creations), alternatives (get-page-history for single page), and when to use pagination. Also notes required rights for patrol-related options.

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

Install Server

Other Tools

Latest Blog Posts

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