Skip to main content
Glama
Notion MCP Server

Notion MCP Server

notion_create_page

Create a new Notion page with a title, optional Markdown content, and an optional parent page ID to organize workspace content.

Instructions

Create a new Notion page

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

Input Schema

NameRequiredDescriptionDefault
titleYesPage title
contentNoPage content in markdown format
parentIdNoParent page ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses nothing beyond the word 'Create' implying a write. It says nothing about the integration/permission requirements to write into a parent, what happens when parentId is omitted, whether the response returns the new page ID, or any side effects.

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

Conciseness3/5

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

The single sentence is front-loaded and contains no filler, which is positive, but here brevity reflects under-specification rather than disciplined concision. Nothing is wasted because nothing extra was said.

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?

For a write tool with zero annotations and no output schema, the definition should clarify where the page is created, what markdown support means in practice, and what the caller receives back. The gap is meaningful because an agent could easily confuse this with appending blocks or updating a page.

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%, with all three properties documented in the schema, so the schema already does the heavy lifting. The description adds no meaning about the title, the markdown content format, or the parent/child relationship for parentId, so it sits at the high-coverage baseline.

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

Purpose2/5

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

The description restates the tool name almost verbatim: 'notion_create_page' becomes 'Create a new Notion page.' It conveys the generic verb and resource, but adds nothing about what kind of page is created, where it lands, or how it differs from notion_update_page or notion_append_blocks, both of which also touch page content.

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?

There is no when-to-use guidance, no exclusions, and no mention of comparable siblings such as notion_update_page (modify an existing page) or notion_append_blocks (add content to an existing page). The agent must infer the selection rule entirely from tool names.

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