Create a new Notion page by copying blocks from a template page, enabling reusable content and consistent page structure.
Create a new page by copying blocks from a template page
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | Title for the new page | |
| parent | Yes | Parent object (database or page) for the new page | |
| properties | No | Additional properties for the new page | |
| template_page_id | Yes | ID of the template page to copy blocks from |
Changes observed during successful MCP inspections.
v1.6.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses that blocks are copied from the template page, which is useful, but it omits permissions needed, whether the template page is modified, rate limits, and error conditions for an invalid template or parent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with zero wasted words. It immediately communicates the core action and mechanism.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the description is too minimal. It does not explain what the tool returns, how failures are handled, or behavioral details beyond the copy mechanism, leaving an agent without enough context to call it correctly in edge cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all four parameters. The description adds no syntax, format, or meaning beyond what the schema provides, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Create), resource (new page), and mechanism (copying blocks from a template page). This distinguishes it from notion_create_page, which creates a page without a template, and from notion_duplicate_page, which duplicates an existing page.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use guidance, no alternatives, and no exclusions. The description implies the tool is used when you want a page based on a template, but it does not mention notion_create_page or notion_duplicate_page as alternatives or specify when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.