Skip to main content
Glama

Move page

wiki_move
Destructive

Move or rename a page and its entire subtree within a wiki. Read the source first and supply its revision. The result's brokenLinks name the pages and records whose links still point at the old path; update them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>",
      "org": "<org>"
    },
    "name": "wiki_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe full path it should have, in the same wiki.
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
fromYesThe page's full path now (general:docs.deploy).
messageNoA brief note on the change describing the move.
ifRevisionNoThe source page revision returned by wiki_read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description goes further by disclosing that the whole subtree moves with the page, that a prior read plus revision is required for safety, and that the response carries brokenLinks identifying stale link sources. That is exactly the post-condition and blast-radius context annotations cannot convey.

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?

Three tight sentences: purpose, prerequisite, and follow-up. The destructive scope and the read-first requirement are front-loaded with zero 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?

With no output schema, the description compensates by naming the brokenLinks field and instructing the agent to update stale references. Combined with annotation disclosure and full schema coverage, an agent has everything needed to invoke this destructive move 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%, so from/to/org/message/ifRevision are already documented in the schema, including the ifRevision-to-wiki_read linkage. The description only reinforces the revision requirement rather than adding format, path syntax, or edge-case detail beyond the schema.

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?

Names a specific verb pair ('move or rename'), a specific resource ('a page and its entire subtree'), and a scope ('within a wiki'). This clearly separates it from editor-style siblings like wiki_edit or wiki_write without needing to name them.

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?

States an explicit prerequisite workflow: read the source first and supply its revision, which routes the agent to wiki_read before calling this. It lacks an explicit 'when not to use' or a named alternative for simpler edits, which keeps it out of 5 territory.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources