mcp-mediawiki-crunchtools

list_recent_changes_tool

Query an authorized MediaWiki instance's revision history and retrieve filtered recent edits by namespace, tag, change type, or start time, returning page titles, authors, comments, and timestamps.

Instructions

List recent edits on the wiki.

Args: namespace: Filter by namespace (default: all namespaces) limit: Maximum results (default: 50, max: 500) tag: Filter by tag name change_type: Filter by type: edit, new, log, categorize, external from_timestamp: Start from this timestamp (ISO 8601)

Returns: List of recent changes with user, title, timestamp, and comment

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tag`	No
`limit`	No
`namespace`	No
`change_type`	No
`from_timestamp`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.1.4Oct 1, 2026
- removedInput schema / properties / change_type / description
```
Removed value: -"Filter by type: edit, new, log, categorize, external"
```
- removedInput schema / properties / from_timestamp / description
```
Removed value: -"Start from this timestamp (ISO 8601)"
```
- removedInput schema / properties / limit / description
```
Removed value: -"Maximum results (default: 50, max: 500)"
```
- removedInput schema / properties / namespace / description
```
Removed value: -"Filter by namespace (default: all namespaces)"
```
- removedInput schema / properties / tag / description
```
Removed value: -"Filter by tag name"
```
Changed5 schema fields changedMay 4, 2026
- addedInput schema / properties / change_type / description
```
Added value: +"Filter by type: edit, new, log, categorize, external"
```
- addedInput schema / properties / from_timestamp / description
```
Added value: +"Start from this timestamp (ISO 8601)"
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results (default: 50, max: 500)"
```
- addedInput schema / properties / namespace / description
```
Added value: +"Filter by namespace (default: all namespaces)"
```
- addedInput schema / properties / tag / description
```
Added value: +"Filter by tag name"
```
First observedv0.1.3Mar 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the return structure ('List of recent changes with user, title, timestamp, and comment') but fails to state that this is a read-only operation, safe to call, or whether results are cached/real-time.

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?

Well-structured with clear Args and Returns sections. Information is front-loaded with the purpose statement. The formatting is slightly formal but efficient, with no redundant sentences.

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 0% schema coverage and lack of annotations, the description adequately covers all parameters and return values. For a read-only listing tool, this is reasonably complete, though it could benefit from a note on pagination behavior or result ordering.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by documenting all 5 parameters. It provides crucial constraints missing from the schema: limit max (500) and default (50), change_type enum values (edit, new, log, categorize, external), and timestamp format (ISO 8601).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List recent edits on the wiki' with a specific verb and resource. It implicitly distinguishes from siblings like list_pages_tool (static pages) and list_user_contributions_tool (user-scoped), though it could explicitly clarify when to use this versus those alternatives.

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

Usage Guidelines2/5

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

No guidance provided on when to use this tool versus siblings like list_user_contributions_tool or get_page_tool (for page history). No prerequisites, rate limit warnings, or filtering recommendations are mentioned.

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