Skip to main content
Glama
ttpears

mediawiki-mcp

by ttpears
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-recent-changes

Retrieve recent edits, page creations, and log events across one or all wikis to monitor activity. Filter by type, namespace, or limit, and paginate through results.

Instructions

Get a feed of recent edits, page creations, and log events across wikis. Returns timestamps, change types, page titles, authors, size deltas, and edit summaries. Useful for monitoring wiki activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by change type
wikiNoWiki name (omit to get changes from all wikis)
limitNoMaximum number of changes
namespaceNoFilter by namespace number
continue_fromNoContinuation token for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.3.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full behavioral burden. It usefully lists return fields (timestamps, change types, page titles, authors, size deltas, edit summaries) in place of an output schema, but omits operational details like auth needs, rate limits, pagination behavior, or the time window covered.

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?

Three front-loaded sentences with no wasted text: purpose, return fields, then usage context. Each sentence contributes distinct information.

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?

The description adequately covers a read-only feed tool with fully documented parameters and no output schema by summarizing return fields. It leaves minor gaps around ordering and time-window behavior, but these are not critical for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so parameter semantics are fully documented in the schema. The description only implies cross-wiki scope via 'across wikis' and adds no syntax, defaults, or filtering guidance beyond the schema.

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?

States a specific verb and resource: 'Get a feed of recent edits, page creations, and log events across wikis.' The cross-wiki scope and feed framing distinguish it from page-specific siblings like get-page-history.

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

Usage Guidelines3/5

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

Says it is 'Useful for monitoring wiki activity,' which implies a use case but does not specify when to choose this over get-page-history, search-page, or other siblings. No alternatives or exclusions are given.

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