Skip to main content
Glama

write_move

Moves a page and its child pages under a new parent, optionally at a specific sibling position; existing links are not rewritten.

Instructions

Move a page (with its children) under another parent; links to it are not rewritten (see write_refactor).

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": {
      "page": "<page>",
      "parent": "<parent>"
    },
    "name": "write_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
parentYesNew parent id or path; "/" for the top level
positionNoIndex among the new siblings; default last

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations declare destructiveHint=false and openWorldHint=false, so safety is partly covered. The description adds real beyond-schema behavior: children move along with the page, and inbound links are left dangling. It still omits whether this requires write permission, whether the move is atomic/reversible, and what happens to the source parent's ordering.

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?

A single sentence with the primary action front-loaded, the child-cascade caveat in parentheses, and the alternative tool routing at the end. No filler or redundant restatement of the name.

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

Completeness4/5

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

For a 3-parameter structural mutation with no output schema, the description covers the key surprise behaviors (child cascade, no link rewriting) that an agent could otherwise get wrong. Only permission requirements and confirmation semantics are absent.

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% and every parameter (page, parent, position) carries its own description including the '/' root convention and the default-last index. The description adds no further parameter meaning, so the baseline 3 applies.

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 (move) and resource (page with its children) plus the target parent, and explicitly contrasts with write_refactor for the link-rewriting case. An agent can distinguish this from write_copy, write_update_page, and write_refactor 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 Guidelines4/5

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

The parenthetical '(see write_refactor)' names the alternative and the condition that selects it — if links must be rewritten, use that tool instead. It gives no guidance on other plausible siblings (write_copy for duplication, write_update_page for field edits), so it is clear but not exhaustive.

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