notion-private-api-mcp

Create Notion Page

create_page

Create a child page under a parent Notion page using Markdown or block JSON input.

Instructions

Create a child page under another page from blocks or Markdown.

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_page_id": "<parent_page_id>",
      "title": "<title>"
    },
    "name": "create_page"
  }
}

Input Schema

Name	Required	Description
`parent_page_id`	Yes	Parent page id or page URL.
`title`	Yes	Title for the new page.
`markdown`	No	Markdown content to convert into blocks.
`blocks`	No	Simplified block JSON.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 31, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'create', which implies mutation, but does not disclose permissions, idempotency, side effects, or output behavior. This is insufficient for a mutation tool.

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?

The description is a single, front-loaded sentence of 14 words with no waste. Every word contributes to understanding the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 4 parameters, the description is minimal. It lacks explanation of return values, error cases, prerequisites, or how markdown vs blocks interact. The agent may be left guessing critical details.

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% with clear descriptions for all parameters. The tool description adds 'from blocks or Markdown', which groups the two optional parameters, but does not add significant new meaning beyond what the schema already provides.

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 tool creates a child page under another page using blocks or Markdown. It uses a specific verb (create) and resource (child page), and distinguishes from siblings like append_blocks and get_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 when to use (when creating a new page as child), but does not provide explicit guidance on when not to use or alternatives. For example, it doesn't mention markdown_to_blocks as a precursor if only conversion is needed.

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

Deploy Server