Notion Advisor

create_page

Add new content to Notion by creating a page inside a database or as a child of an existing page. Specify title, optional markdown content, and database properties to structure the new page.

Instructions

Create a new page in a database or as a child of another page. Use when user wants to add new content to Notion.

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

Input Schema

Name	Required	Description
`title`	Yes	Page title
`content`	No	Initial page content in markdown format
`parent_id`	Yes	Parent database ID or page ID
`properties`	No	Database properties (for database parents)
`parent_type`	Yes	Type of parent

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It does clarify that the page can be created in a database or as a child, but it says nothing about failure cases, permissions, side effects of creation, or what happens when invalid parent IDs are supplied.

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?

Two short sentences with the core purpose front-loaded. The second sentence provides a usage hint, though it is imprecise and arguably could be sharpened to reference creating a page rather than generic 'new content.'

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

Completeness3/5

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

For a simple create tool, the description plus full schema coverage is mostly adequate. However, there is no output schema, no mention of what the response contains, and no guidance about required parent constraints or nested properties, leaving some ambiguity for an agent deciding what to pass.

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 description coverage is 100%, so the schema already documents all parameters. The description adds modest context by mapping 'in a database or as a child' to the parent_type enum, but it does not explain semantic relationships between properties, content, and parent types beyond what the schema states.

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 states a specific verb and resource ('Create a new page') and clarifies the two kinds of parents: a database or another page. However, it doesn't explicitly distinguish itself from append_blocks, which also adds content to Notion in a different way.

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 phrase 'Use when user wants to add new content to Notion' gives some usage context but is overly broad and could lead an agent toward create_page when append_blocks is the correct choice. No alternatives or exclusions are mentioned.

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

Deploy Server