Skip to main content
Glama
ProfessionalWiki

mediawiki-mcp-server

by ProfessionalWiki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create-page

Idempotent

Create a new wiki page with supplied content and receive its title, page ID, and first revision ID. Fails if the page exists; for updates, use update-page.

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

TableJSON Schema
NameRequiredDescriptionDefault
botNoMarks 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.
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.15.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. 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"
+}
  3. 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"
+}
  4. Addedv1.0.2
  5. Removedv1.0.1
  6. 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"
  7. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The description adds meaningful operational behavior beyond the annotations: it discloses that the call fails on duplicate titles, describes the returned identifiers, explains the contentModel fallback to namespace default, and suggests chunked appends for large content. The annotations already cover readOnly, destructive, and idempotent hints, and the description does not contradict them.

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?

The description is four sentences, each carrying distinct information: action and return values, duplicate failure and alternative, contentModel semantics, and large-page chaining. It is compact and front-loaded with the core outcome, though slightly longer than strictly necessary.

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?

Despite the absence of an output schema, the description specifies the returned fields and the key error condition. With full parameter documentation in the schema and the explicit pointer to update-page for existing pages and large-content workflows, the description gives an agent everything needed to invoke this tool correctly.

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?

With 100% schema description coverage, the baseline is 3, but the description adds useful meaning to contentModel by giving examples ('javascript, css') and clarifying the namespace-default behavior. It also ties source to the contentModel format, which slightly exceeds what the schema alone states.

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 opens with a specific verb-object pair ('Creates a new wiki page') and immediately states the return values: title, page ID, and first revision ID. It also distinguishes itself from the sibling tool by saying 'for existing pages, use update-page', so an agent can tell this apart from update-page, move-page, delete-page, or undelete-page.

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?

The description explicitly states when not to use the tool: 'Fails if a page with the given title already exists; for existing pages, use update-page.' It also gives a concrete pattern for large pages by pairing create-page with chained update-page(operation='append') calls, providing clear guidance on when and how to use it versus alternatives.

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