notion-mcp-server

move-page

Move a page to a new parent page or data source. Provide the page ID and target parent ID.

Instructions

Move a page to a new parent (page or data source). Provide either page_id or data_source_id as the new parent. Returns page ID and URL. (API version 2025-09-03)

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_id": "<page_id>",
      "parent": "<parent>"
    },
    "name": "move-page"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes	Page ID
`parent`	Yes	Parent (provide either page_id or data_source_id)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.14.0May 27, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the burden. It mentions return values (page ID and URL) and API version, but does not disclose behavioral traits like what happens to page children or whether the operation is destructive.

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?

Two sentences, front-loaded with action, includes essential information (parent options, return values, API version). No superfluous words.

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?

Given the tool's complexity (2 parameters, nested object, no output schema, no annotations), the description is largely complete, covering purpose, parameters, and return. Could mention effect on children or immediate execution for full completeness.

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% with descriptions for each property. The description adds value by clarifying that either page_id or data_source_id should be provided inside the parent object, and states the return values, going 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?

The description clearly states the action ('Move a page') and the resource ('to a new parent'), specifying two possible parent types (page or data source). This distinguishes it from sibling tools like update-page or archive-page.

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

Usage Guidelines3/5

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

The description implies how to use the tool by mentioning 'Provide either page_id or data_source_id', but does not explicitly state when to use this tool vs alternatives like update-page, nor does it mention prerequisites or exclusions.

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