notion-full-mcp

Overview Schema Source Related Servers Discussions Admin

create_page

Create a new Notion page under a parent page or database, setting its title, icon, initial content blocks, and database properties in one call.

Instructions

Create a new Notion page under a parent page or database.

Args: parent_id: ID of the parent page or database. title: Title for the new page. parent_type: "page_id" (default) or "database_id". icon_emoji: Optional emoji character to use as the page icon. children_json: Optional JSON array of block objects for initial content. properties_json: Optional JSON object of additional database properties to set. Example for setting Status: {"Status": {"status": {"name": "Done"}}} Example for setting Date: {"Due date": {"date": {"start": "2026-04-15"}}}

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": {
      "parent_id": "<parent_id>",
      "title": "<title>"
    },
    "name": "create_page"
  }
}

Input Schema

Name	Required	Default
`title`	Yes
`parent_id`	Yes
`icon_emoji`	No
`parent_type`	No	page_id
`children_json`	No
`properties_json`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1May 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful structural behavior, namely that the parent may be a page or a database and that database properties can be set at creation time, but says nothing about required integration permissions, error modes, or what happens when a database parent is used without properties_json.

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?

The purpose sentence is front-loaded and the Args list is compact and scannable, with the two examples earning their space by resolving the trickiest parameter. It is slightly list-heavy, but no sentence is filler given the zero schema coverage.

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 an output schema present and annotations covering safety, the description is complete enough for execution: it explains parent selection, initial content, and database properties. The remaining omission, permission prerequisites and the exact children_json block format, is a moderate gap rather than a blocker.

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 description coverage is 0%, so the description carries the full burden, and it does so by defining all six parameters, including the enum-like values for parent_type and two concrete properties_json examples for Status and Date. Minor gaps remain, such as the expected shape of children_json, which is only described as a JSON array of block objects.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource+scope: 'Create a new Notion page under a parent page or database.' That is enough for an agent to distinguish it from mutating siblings like append_blocks_to_page or update_page, though it never names an alternative explicitly.

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?

Usage is only implied by the tool's purpose; there is no explicit when-to-use versus when-not, and no guidance on choosing this over copy_page_to_parent or append_blocks_to_page for adding content. The parent_type default ('page_id') is the only routing aid offered.

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