Skip to main content
Glama

mediawiki_get_recent_changes

Read-onlyIdempotent

Retrieve recent changes across the entire wiki, including timestamps, users, and edit summaries. Filter by time range, namespace, or change type, and optionally aggregate 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

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
changesNo
has_moreYes
aggregatedNo
continue_fromNo
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds behavioral context: default limit, aggregation behavior, and response summary. No contradictions.

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?

The description is well-structured with clear sections (main, USE WHEN, NOT FOR, PARAMETERS, RETURNS). It is concise, front-loaded, and every sentence adds value.

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?

With an output schema present, the description appropriately summarizes return values. It covers purpose, usage, parameters, and output, leaving no important gaps given the tool's complexity.

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 coverage is 100% with good descriptions. The description adds a PARAMETERS section summarizing key parameters, but adds limited new detail beyond the schema. Still, it helps by grouping and clarifying aggregation behavior.

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 starts with 'Get recent changes across the entire wiki', specifying a clear verb and resource. It lists use-case examples and explicitly distinguishes from siblings like mediawiki_get_revisions and mediawiki_get_user_contributions.

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 includes 'USE WHEN' and 'NOT FOR' sections with explicit alternative tool names, providing unambiguous guidance on when to use this tool instead of others.

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/olgasafonova/mediawiki-mcp-server'

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