Skip to main content
Glama

update-page

DestructiveIdempotent

Replace a wiki page's content with full source, a section edit, or an append/prepend delta. Uses revision IDs for edit-conflict detection to prevent overwriting concurrent changes.

Instructions

Replaces the existing content of a wiki page and returns the new revision ID. Fails if the page does not exist; for new pages, use create-page. Pass latestId (obtained from get-page with metadata=true) to enable edit-conflict detection: if the page has been edited since that revision, the update is rejected rather than silently clobbering concurrent changes. For large pages, three modifiers avoid shipping the full source: section=N edits one section (pairs with get-page section=N for reads), section='new' adds a new heading section, and mode='append' or 'prepend' sends a delta. Each call is a separate revision; for chains of mode='append' calls, re-fetching latestId between calls confirms the previous chunk landed before the next.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesWiki page title
sourceYesThe content to write, in the existing page's content model. Interpreted as the full page by default; as the given section's content when section is set; or as a delta (appended or prepended) when mode is set.
latestIdNoBase revision ID for edit-conflict detection; obtain from get-page with metadata=true. If omitted, the update is applied without conflict detection.
commentNoSummary of the edit
sectionNoSection to edit: 0 (lead), 1..N (existing heading sections), or 'new' to append a new heading section.
modeNoAdds source to the existing content instead of replacing it: 'append' to the end, 'prepend' to the start.
sectionTitleNoHeading for a new section; required when section='new', rejected otherwise.
Behavior5/5

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

Adds behavior beyond annotations: fails if page missing, conflict detection with latestId, separate revision per call, section/mode behavior. Annotations already indicate destructive but description provides critical context.

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?

Well-structured, front-loaded with main action, then optional modifiers. Every sentence adds value without redundancy. Efficient for the information density.

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 no output schema, description mentions return of revision ID, covers failure conditions, conflict detection, and all parameter interactions. Complete for a complex tool with 7 params.

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?

Schema coverage is 100%, but description enriches each parameter: explains latestId usage, section values (0..N or 'new'), mode as delta, sectionTitle required when section='new'. Adds meaning beyond 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?

Description clearly states it replaces content of an existing wiki page and returns a new revision ID, distinguishing from create-page for new pages. Verb 'replaces' and resource 'existing content' are specific.

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 says to use for existing pages, not for new (use create-page). Provides guidance on edit-conflict detection with latestId, and for large pages with section and mode. Covers when to use alternatives.

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/ProfessionalWiki/MediaWiki-MCP-Server'

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