mcp-notion-fast

Create page

create_page

Create a Notion page under a specified parent. Add properties, content blocks, icons, and covers to structure information.

Instructions

Create a Notion page under a page or data source parent.

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": "<parent>",
      "properties": "<properties>"
    },
    "name": "create_page"
  }
}

Input Schema

Name	Required	Description	Default
`icon`	No
`cover`	No
`parent`	Yes
`children`	No
`properties`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`code`	No
`data`	No
`error`	No
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already indicate a non-read, non-idempotent, non-destructive operation. The description adds no additional behavioral context, such as effects on the parent, required permissions, atomicity, or response behavior. It only repeats the basic create action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief ('Create a Notion page under a page or data source parent.'). While concise, it is under-specified for a tool with 5 parameters and nested objects, crossing from conciseness into incompleteness.

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?

The description lacks essential context for correct usage, such as how to structure properties for database parents, valid parent types, or that children blocks can be included. Given the tool's complexity and 0% schema coverage, this is a substantial gap.

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

Parameters1/5

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

Input schema has 5 parameters with 0% description coverage. The description mentions only 'parent' context and fails to explain properties, children, icon, cover, or their relationships. It does not compensate for the missing schema documentation.

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 clearly states a specific action ('Create a Notion page') with a constrained parent context ('under a page or data source parent'). It distinguishes from sibling tools like update_page or delete_block. However, it doesn't fully differentiate from hypothetical create tools in other contexts and uses the slightly technical term 'data source parent'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. The description gives context ('under a page or data source parent') but doesn't mention exclusions or alternatives. Siblings like append_block_children or update_page are not referenced.

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

Deploy Server