Skip to main content
Glama

move-page

DestructiveIdempotent

Rename a wiki page to a new title, with options to move its talk page, subpages, and control redirect behavior.

Instructions

Renames a wiki page, moving it — and by default its talk page — to a new title, and returns the old and new titles plus whether a redirect was left behind. By default leaves a redirect at the old title; set leaveRedirect=false to suppress it (requires the suppressredirect right, otherwise the redirect is left regardless). Fails if the source page does not exist, if the target title already exists (unless it is a redirect and ignoreWarnings is set), or if the authenticated user lacks the move permission. Moving a File page additionally requires the file-move permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromTitleYesCurrent title of the wiki page to move
toTitleYesNew title to move the page to
commentNoReason for the move
moveTalkNoAlso move the associated talk page
moveSubpagesNoAlso move subpages, where the namespace allows subpages
leaveRedirectNoLeave a redirect at the old title. Suppressing it requires the suppressredirect right; without that right MediaWiki leaves the redirect regardless.
ignoreWarningsNoProceed past move warnings, e.g. when the target is an existing redirect. Moving over a non-redirect page still fails.
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.
Behavior5/5

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

Annotations provide destructiveHint and idempotentHint, but the description adds rich behavioral detail: default redirect behavior, suppressredirect right requirement, talk page and subpage handling, failure conditions. No contradiction with annotations; it significantly enhances transparency.

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 a single paragraph that efficiently conveys key points without excessive verbosity. It is front-loaded with the main action. However, it could be slightly improved with bullet points for readability, so not a perfect 5.

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 moderate complexity (8 parameters, 2 required) and no output schema, the description covers all necessary context: input requirements, default behaviors, failure conditions, permissions, and return values. It is fully adequate for an AI agent to invoke 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 coverage is 100% with each parameter described adequately. The description adds context (e.g., permission requirement for leaveRedirect) but does not provide new meaning beyond the schema. Baseline 3 is appropriate as the description neither harms nor significantly enhances parameter understanding.

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 it renames a wiki page, moving it and its talk page by default, and returns old/new titles plus redirect info. This distinguishes it from sibling tools like create-page, delete-page, or update-page by specifying the unique action of moving/renaming.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description details conditions for failure (source missing, target exists, permissions) and default behaviors (redirect left, talk page moved). While it doesn't explicitly contrast with alternatives, the context makes the tool's purpose clear and provides sufficient guidance for when to use it.

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/ProfessionalWiki/MediaWiki-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server