Skip to main content
Glama
cphoskins
by cphoskins

copy_page_to_parent

Recreate a page under a new parent by copying its title, icon, and content, then archive the original. Works around Notion's lack of move support.

Instructions

Recreate a page under a new parent (destructive workaround for move).

Since Notion's public API does not support changing a page's parent, this tool works around the limitation by creating a new page at the target location with the same title, icon, and content, then archiving the original.

LIMITATIONS (read carefully): * Block IDs of the new page are different from the original. Any external references to original block IDs (graphics-spec.md, cross-page links, Change Log entries) will point at the archived original and need to be updated. * file_upload image blocks are copied as external URL references using the Notion-signed URL returned at copy time. Those URLs expire within an hour. For permanent preservation, re-upload the source files via upload_image_as_block after the copy. * child_page descendants (nested subpages) are NOT recursively copied -- the tool refuses to run if any are present. Copy them individually. * Comments, page history, permissions, and synced blocks are not copied.

Args: page_id: The source page to copy. new_parent_id: The target parent page or database ID. parent_type: "page_id" (default) or "database_id". archive_original: If True (default), archive the source page after the copy completes. Set False to keep both copies side-by-side.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYes
new_parent_idYes
parent_typeNopage_id
archive_originalNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, description fully discloses destructive behavior (archive original), block ID regeneration, file URL expiration, refusal on nested subpages, and omitted elements like comments and permissions.

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?

Well-structured with overview, limitations list, and args section. Slightly lengthy but all content is valuable for a complex tool.

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?

Description covers purpose, usage, behavioral details, and parameter meanings comprehensively. Output schema exists so omission of return values is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, description provides clear semantics for all 4 parameters including defaults, explaining why archive_original defaults True and parent_type options.

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?

Description clearly states it recreates a page under a new parent as a destructive workaround for move. Distinguishes from sibling 'move_page' by explaining the API limitation.

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

Usage Guidelines5/5

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

Explicitly says when to use (when API doesn't support parent change) and provides limitations (block ID change, URL expiry, no recursive copy, what's not copied). Implies alternatives for child pages and file preservation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cphoskins/notion-full-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server