Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

notion-mcp__notion_move_page

Destructive

Moves one Notion page to a new parent: another page, or a data source (where it becomes a row). Pages only; Notion's API does not move databases or other blocks. Returns the page's id, url and new parent.

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>"
    },
    "name": "notion-mcp__notion_move_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
page_idYesThe page's Notion id, with or without dashes, or a Notion URL that contains it (the id is read from the URL).
parent_page_idNoThe parent page's Notion id or URL. Exactly one of parent_page_id and parent_data_source_id is set.
parent_data_source_idNoThe parent data source's Notion id (notion_get_database lists a database's data sources). The page becomes a row of it. Exactly one of parent_page_id and parent_data_source_id is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, and the description usefully adds the destination semantics (page becomes a row of the data source) plus the return payload. It stops short of mutation-risk context such as whether the page leaves its old parent, what happens to existing content, or the permission requirement that both source and destination be shared with the integration.

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 short sentences, front-loaded with the action and destination, then the constraint, then the return value. Nothing redundant or padded.

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?

With no output schema, the description compensates by naming the returned fields (id, url, new parent) and states the block-type limitation. Only the permission/integration-access prerequisite for a cross-parent move is unaddressed, which is a minor gap for a destructive mutation.

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 all four parameters are already documented, including the exactly-one-of relationship. The description only reinforces which parameter forms a row rather than adding new syntax or format detail, 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 and resource ('Moves one Notion page') and narrows the destination to 'another page, or a data source (where it becomes a row)'. This clearly separates it from siblings like notion_update_page or notion_duplicate_page, which don't change parentage.

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?

Gives an explicit negative boundary — 'Pages only; Notion's API does not move databases or other blocks' — which tells an agent when the tool will fail. It does not, however, name a sibling for adjacent tasks (e.g. changing properties vs. relocating), leaving some routing to inference.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources