mcp-mediawiki-crunchtools

Move Page Tool

move_page_tool

Rename or move a wiki page to a new title, optionally moving its talk page and controlling redirects. Requires authentication.

Instructions

Move (rename) a wiki page. Requires authentication.

Input Schema

TableJSON Schema

Name	Required	Description
`reason`	No	Reason for move (default: empty)
`to_title`	Yes	New page title
`move_talk`	No	Also move the talk page (default: True)
`from_title`	Yes	Current page title
`no_redirect`	No	Do not create a redirect (default: False)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.2.1Oct 22, 2026
- addedInput schema / properties / from_title / description
```
Added value: +"Current page title"
```
- addedInput schema / properties / move_talk / description
```
Added value: +"Also move the talk page (default: True)"
```
- addedInput schema / properties / no_redirect / description
```
Added value: +"Do not create a redirect (default: False)"
```
- addedInput schema / properties / reason / description
```
Added value: +"Reason for move (default: empty)"
```
- addedInput schema / properties / to_title / description
```
Added value: +"New page title"
```
Changed5 schema fields changedv0.1.4Oct 1, 2026
- removedInput schema / properties / from_title / description
```
Removed value: -"Current page title"
```
- removedInput schema / properties / move_talk / description
```
Removed value: -"Also move the talk page (default: True)"
```
- removedInput schema / properties / no_redirect / description
```
Removed value: -"Do not create a redirect (default: False)"
```
- removedInput schema / properties / reason / description
```
Removed value: -"Reason for move (default: empty)"
```
- removedInput schema / properties / to_title / description
```
Removed value: -"New page title"
```
Changed5 schema fields changedMay 4, 2026
- addedInput schema / properties / from_title / description
```
Added value: +"Current page title"
```
- addedInput schema / properties / move_talk / description
```
Added value: +"Also move the talk page (default: True)"
```
- addedInput schema / properties / no_redirect / description
```
Added value: +"Do not create a redirect (default: False)"
```
- addedInput schema / properties / reason / description
```
Added value: +"Reason for move (default: empty)"
```
- addedInput schema / properties / to_title / description
```
Added value: +"New page title"
```
First observedv0.1.3Mar 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it only discloses the auth requirement. For a mutation tool it omits what an agent most needs: that a redirect is left behind by default (no_redirect=false), that the talk page is moved by default, and that history/links are affected by the rename.

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?

Two short sentences with zero filler and the core action is front-loaded. The brevity is efficient but edges toward under-specification given the tool mutates page identity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return-value explanation is not required, but for a 5-parameter mutating tool with no annotations the description is thin: it never mentions redirect creation, talk-page handling, or failure conditions such as title collisions.

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 every parameter including defaults is already documented in the schema; the description adds no parameter-level meaning. A baseline 3 is appropriate, though a note that to_title must not collide with an existing page would have earned more.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Move (rename) a wiki page') and usefully disambiguates that move means rename, which an agent could otherwise misread as a file-system move. It does not distinguish itself from siblings like edit_page_tool or delete_page_tool, which a Wiki-API-literate agent must infer.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus editing a page title or creating a new page under a different title, nor on preconditions such as page existence or conflicting target titles. The only stated condition is 'Requires authentication', which is a prerequisite, not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.