Skip to main content
Glama
Sign In
mediawiki-mcp-server

mediawiki-mcp-server

by ProfessionalWiki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create-page

Idempotent

Creates a new MediaWiki page from a title and content, returning the new title, page ID, and first revision ID; fails if the title already exists.

Instructions

Creates a new wiki page with the provided content and returns the new page's title, page ID, and first revision ID. Fails if a page with the given title already exists; for existing pages, use update-page. The optional contentModel parameter selects a non-default content format (e.g. javascript, css); when omitted, MediaWiki picks the default for the title's namespace. For building up a large page across multiple calls, pair create-page with chained update-page(operation='append') calls, each adding a chunk.

Input Schema

NameRequiredDescriptionDefault
botNoMarks the edit as a bot edit, which Special:RecentChanges hides by default. When omitted, the bot setting of the wiki decides; pass false to leave one edit unflagged. Applies only if the account has the `bot` right and, through a bot password or OAuth consumer, the High-volume (bot) access grant; otherwise the edit saves unflagged and the response reports botMarked: false. Use for bulk or automated edits, or when the user asks.
wikiNoWiki to target, as a key from the mcp://wikis/ resources (e.g. en.wikipedia.org), or the full mcp://wikis/ URI. Omit to use the default wiki.
titleYesWiki page title
sourceYesPage content in the format specified by the contentModel parameter
commentNoReason for creating the page
contentModelNoContent model of the new page. If omitted, MediaWiki picks the default for the title's namespace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.21.0
    • changedInput schema / properties / bot / description
      Previous value: -"Marks the edit as a bot edit, which Special:RecentChanges hides by default. Takes effect only when the authenticated account has the `bot` right (granted by the bot group, or by the high-volume grant on a bot password or OAuth consumer); without it the edit saves unflagged and the response reports botMarked: false. Use when performing bulk or automated edit runs, or when the user requests it."New value: +"Marks the edit as a bot edit, which Special:RecentChanges hides by default. When omitted, the bot setting of the wiki decides; pass false to leave one edit unflagged. Applies only if the account has the `bot` right and, through a bot password or OAuth consumer, the High-volume (bot) access grant; otherwise the edit saves unflagged and the response reports botMarked: false. Use for bulk or automated edits, or when the user asks."
  2. Changed1 schema field changedv0.15.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / bot
      Added value: +{
+  "description": "Marks the edit as a bot edit, which Special:RecentChanges hides by default. Takes effect only when the authenticated account has the `bot` right (granted by the bot group, or by the high-volume grant on a bot password or OAuth consumer); without it the edit saves unflagged and the response reports botMarked: false. Use when performing bulk or automated edit runs, or when the user requests it.",
+  "type": "boolean"
+}
  4. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / wiki
      Added value: +{
+  "description": "Wiki to target, as a key from the mcp://wikis/ resources (e.g. en.wikipedia.org), or the full mcp://wikis/ URI. Omit to use the default wiki.",
+  "type": "string"
+}
  5. Addedv1.0.2
  6. Removedv1.0.1
  7. Changed3 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / contentModel / default
      Added value: +"wikitext"
    • changedInput schema / properties / contentModel / description
      Previous value: -"Type of content on the page. Defaults to \"wikitext\""New value: +"Type of content on the page"
  8. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is largely covered. The description adds real behavioral context on top: the duplicate-title failure mode, the default content-model resolution by namespace, and the chunked-creation workflow. It stops short of mentioning permissions/auth needs (deferred to the bot param in the schema), which keeps it from a 5.

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

Conciseness4/5

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

Front-loaded with the action and return values, then failure/alternative, then parameter nuance, then workflow. Every sentence carries information, though the final workflow sentence is somewhat tangential and could be trimmed for tighter focus.

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?

There is no output schema, but the description explicitly enumerates the return values, and for a 6-parameter creation tool with full schema coverage the remaining gaps are minimal. An agent has enough to call it correctly and interpret the result.

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%, so the baseline is 3. The description nonetheless adds meaning for contentModel beyond the schema: it gives example non-default formats (javascript, css) and explains that omission defers to the namespace default, which clarifies the practical effect of leaving it out.

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 ('Creates a new wiki page with the provided content') and immediately names what it returns (title, page ID, first revision ID). It also distinguishes itself from the sibling 'update-page' by scoping itself to new pages only.

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?

Gives an explicit when-not: 'Fails if a page with the given title already exists; for existing pages, use update-page.' It also describes a concrete alternative workflow (chained update-page append calls) for the large-page case, so the agent knows both the boundary and the composition pattern.

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