Skip to main content
Glama
ttpears

mediawiki-mcp

by ttpears
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update-page

Update an existing wiki page by applying diffs, editing sections, appending, prepending, or replacing content. Requires page title and edit summary.

Instructions

Update an existing wiki page. WORKFLOW: First call get-page to read the current wikitext source, then call this tool with your changes.

EDIT MODES (use exactly one): • diff: Preferred for targeted edits. Provide a unified diff (with @@ hunk headers and context lines) — the server fetches current content, applies the patch, and saves. Best for surgical changes to large pages. • section + content: Edit a single section by number (0 = lead section). Only that section is replaced. • append: Add text to the end of the page without reading current content first. • prepend: Add text to the beginning of the page without reading current content first. • content: Full page replacement. Avoid for large pages — use diff instead.

WIKITEXT STYLE GUIDE — when writing or updating wikitext, use modern syntax: • Tables: {| class="wikitable" with |- row separators (not |---- or border="1" or HTML ) • Bold/italic: '''bold''' and ''italic'' (not /) • Headings: == Level 2 == through ====== Level 6 ====== (skip level 1) • Lists: * bullets, # numbered, ; and : for definition lists • Links: [URL description] for external (not bare URLs) • Avoid deprecated tags: , , , , , • Avoid deep colon indentation (::), excessive , inline CSS on divs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diffNoUnified diff to apply to the page. Server fetches current content, applies the patch, and submits. Use standard unified diff format with @@ hunk headers. Context lines help match the right location
userNoName of the person requesting this edit (for attribution in edit summary). Ask the user if not known
wikiNoWiki name (uses default if omitted)
titleYesPage title
appendNoText to append to the end of the page
contentNoFull page content for complete replacement. Avoid for large pages — use diff instead
prependNoText to prepend to the beginning of the page
sectionNoSection number to edit (0 = lead section). Use with content to replace only that section
summaryYesEdit summary

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

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the server-side fetch/apply/save flow for diff, the section-replacement semantics, and content-replacement scope. It omits mutation-confirmation, revertability, and auth/permission requirements, but the core behavioral mechanics of each mode are well covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Front-loaded with the workflow and mode guidance, which earns its place. However, the 11-line wikitext style guide is largely tangential to invoking this tool and bloats the definition; it reads as reference material rather than invocation guidance.

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?

For a 9-parameter mutation tool with no annotations and no output schema, the description covers workflow, mode selection, and edit semantics well enough to invoke correctly. Missing permission/attribution caveats (the 'user' param notes attribution) and confirmation behavior are the main gaps.

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 the schema already documents all 9 parameters. The description adds mode-selection semantics (e.g., 'append... without reading current content first') beyond the schema, but does not add parameter-level syntax detail beyond what the schema provides.

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+resource ('Update an existing wiki page') and immediately differentiates the edit modes, which distinguishes it from siblings like create-page and delete-page that share the page resource.

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 names the workflow prerequisite (call get-page first) and provides a clear decision framework: 'use exactly one' of diff/section+content/append/prepend/content, with 'Preferred' and 'Avoid for large pages' guidance. This is textbook when-to-use guidance.

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