Skip to main content
Glama

mediawiki_move_page

Destructive

Move or rename a wiki page from one title to another, optionally moving associated talk pages and subpages. Creates a redirect from the old title by default.

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

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
toYes
fromYes
reasonNo
messageYes
successYes
talk_movedNo
redirect_urlNo
Behavior5/5

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

Discloses side effect (creates redirect), permissions requirement, and default behaviors. Annotations include destructiveHint=true; description does not contradict and adds 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 with a clear purpose, usage guidance, parameter list, return value, and warning. Every section is concise and informative.

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?

Covers all necessary aspects: purpose, usage, parameters, return values, permissions, and side effects. Sufficient for a complex tool with 7 parameters and no output schema.

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%, but description adds value by listing parameters with defaults and practical notes (e.g., 'requires suppressredirect right' for no_redirect).

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?

Explicitly states 'Move (rename) a wiki page' with clear verb and resource. Differentiates from siblings in 'NOT FOR' section by naming mediawiki_edit_page and mediawiki_find_replace.

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?

Provides specific 'USE WHEN' examples and a 'NOT FOR' section with explicit alternatives, giving clear guidance on when to use this tool vs others.

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