Skip to main content
Glama
olgasafonova

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_move_page

Destructive

Rename a wiki page, create a redirect from the old title, and optionally move its talk page or subpages. Use when changing a page title without editing page content.

Instructions

Move (rename) a wiki page. Creates a redirect from the old title.

USE WHEN: User says "rename the page", "move X to Y", "change the page title".

NOT FOR: Editing page content (use mediawiki_edit_page or mediawiki_find_replace).

PARAMETERS:

  • from: Current page title (required)

  • to: New page title (required)

  • reason: Reason for the move (optional)

  • no_redirect: Don't create redirect from old title (default false)

  • move_talk: Also move the talk page (default true)

  • move_subpages: Also move subpages (default false)

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

WARNING: Requires authentication (bot password) and move permissions. Creates a redirect from the old title by default.

Input Schema

NameRequiredDescriptionDefault
toYesNew page title
fromYesCurrent page title
reasonNoReason for the move
move_talkNoAlso move the talk page if it exists (default true)
rationaleYesRequired one-sentence explanation of why you are making this change. Stored in the audit log for post-hoc intent reconstruction.
no_redirectNoDon't create a redirect from the old title (requires suppressredirect right)
move_subpagesNoAlso move subpages if they exist

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
reasonNo
messageYes
successYes
talk_movedNo
redirect_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.31.0
    • addedInput schema / properties / rationale
      Added value: +{
+  "description": "Required one-sentence explanation of why you are making this change. Stored in the audit log for post-hoc intent reconstruction.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "from",
-  "to"
-]New value: +[
+  "rationale",
+  "from",
+  "to"
+]
  2. Addedv1.30.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description adds substantive context beyond them: the default redirect creation, the required authentication (bot password) and move permissions, and that the result includes revision ID, diff URL and undo instructions. This is exactly the extra behavioral detail the annotations cannot carry.

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?

Front-loaded with the core action, then cleanly sectioned into USE WHEN / NOT FOR / PARAMETERS / RETURNS / WARNING. Every line adds an actionable fact with no filler.

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?

For a destructive, auth-gated mutation tool the definition covers side effects, permissions, defaults, alternatives and return shape; with an output schema present it does not need to enumerate return fields. An agent has everything needed to call it correctly.

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 every parameter including defaults, making the PARAMETERS list largely redundant (baseline 3). The description also omits the required 'rationale' parameter entirely, a small gap against the schema's audit-log intent field.

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 ('Move (rename) a wiki page') and immediately clarifies the side effect ('Creates a redirect from the old title'). The NOT FOR clause routes the agent to the correct siblings for content edits, so it is distinguishable from mediawiki_edit_page without opening any schema.

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?

An explicit USE WHEN block gives triggering user phrases, and a NOT FOR block names alternatives (mediawiki_edit_page, mediawiki_find_replace) with the condition that selects them. Nothing is left to inference.

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