Skip to main content
Glama

mediawiki_compare_revisions

Read-onlyIdempotent

Compare two page revisions and display an HTML diff with additions highlighted in green and deletions in red. Use when you need to view changes between different versions of a wiki page.

Instructions

Compare two revisions and show the diff.

USE WHEN: User asks "what changed between versions", "show the diff", "compare old and new".

NOT FOR: Just listing revisions (use mediawiki_get_revisions). Not for comparing a topic across pages (use mediawiki_compare_topic).

PARAMETERS:

  • from_rev: Source revision ID, OR

  • from_title: Source page title (uses latest revision)

  • to_rev: Target revision ID, OR

  • to_title: Target page title

RETURNS: HTML-formatted diff showing additions (green) and deletions (red).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.
from_revNoSource revision ID
to_revNoTarget revision ID
from_titleNoSource page title (uses latest revision)
to_titleNoTarget page title (uses latest revision)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_titleYes
from_revidYes
to_titleYes
to_revidYes
diffYes
from_userNo
to_userNo
from_timestampNo
to_timestampNo
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. The description adds that the tool returns an HTML-formatted diff with colored additions/deletions, providing useful 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.

Conciseness5/5

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

The description is concise, well-structured with clear headings (USE WHEN, NOT FOR, PARAMETERS, RETURNS), and front-loads essential information in two sentences.

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?

Given the tool's moderate complexity, full schema coverage, and presence of output schema and annotations, the description covers all necessary aspects: usage context, parameter roles, return type, and exclusions.

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% (baseline 3). The description groups parameters with 'OR' logic and clarifies that from_title/to_title use the latest revision, adding meaning beyond the schema descriptions.

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 explicitly states 'Compare two revisions and show the diff' and distinguishes from siblings like mediawiki_get_revisions (for listing) and mediawiki_compare_topic (for comparing across pages).

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?

Clearly states 'USE WHEN' scenarios and 'NOT FOR' cases with specific alternative tool names (mediawiki_get_revisions, mediawiki_compare_topic).

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