Skip to main content
Glama

mediawiki_edit_page

Destructive

Create or rewrite entire wiki page content. Specify a section to edit only part of the page; otherwise, the full content is replaced.

Instructions

Create new pages or rewrite entire page content.

USE WHEN: User says "create a new page", "rewrite the entire About page", "replace all content".

NOT FOR: Simple text changes (use mediawiki_find_replace). Not for formatting (use mediawiki_apply_formatting).

PARAMETERS:

  • title: Page name (required)

  • content: New page content (required)

  • section: Edit specific section only (optional)

  • summary: Edit summary (required for good practice)

  • minor: Mark as minor edit (default false)

  • bot: Mark as bot edit (default false)

RETURNS: Includes revision ID, diff URL, and undo instructions.

WARNING: This overwrites entire page content unless section is specified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rationaleYesRequired one-sentence explanation of why you are making this change. Stored in the audit log for post-hoc intent reconstruction.
titleYesPage title to edit or create
contentYesNew page content in wikitext format
summaryNoEdit summary explaining the change
minorNoMark as minor edit
botNoMark as bot edit (requires bot flag)
sectionNoSection to edit ('new' for new section, number for existing)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYes
titleYes
page_idYes
revision_idYes
new_pageYes
messageYes
Behavior5/5

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

Description warns about overwriting content, explains return values (revision ID, diff URL, undo instructions), and aligns with annotations (destructiveHint=true, openWorldHint=true). No contradictions.

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-organized with clear sections (purpose, usage, parameters, returns, warning). Every sentence serves a purpose with no redundancy.

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 complexity (7 params, output schema exists) and sibling count (45 tools), the description adequately covers purpose, behavioral warnings, and return details. Annotations and schema handle remaining context.

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 coverage is 100%, so baseline is 3. The description adds minor value by noting that summary is 'required for good practice' and minor/bot defaults, but omits mention of the required 'rationale' parameter, which is only in 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?

The description clearly states the tool creates new pages or rewrites entire content, using specific verbs and resources. It distinguishes from sibling tools like mediawiki_find_replace and mediawiki_apply_formatting.

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 provides 'USE WHEN' scenarios and 'NOT FOR' exclusions with specific sibling tool references, leaving no ambiguity about when to use this tool.

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