Skip to main content
Glama
Sign In
notion-plus-mcp-server

notion-plus-mcp-server

by katekruger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Page

notion_create_page

Create a Notion page or sub-page under a parent database or page, with schema-validated properties, templates, icons, covers, and markdown or block content.

Instructions

Create a page. If parent is a database, properties are validated against its schema (same rules as notion_update_properties) and title fills the title property; template applies one of the database's templates (see notion_list_templates). If parent is a page, a sub-page is created. Content can be markdown or structured blocks (same formats as notion_insert_blocks). icon is an emoji, image URL, or local image path; cover is an image URL or local path.

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

Input Schema

NameRequiredDescriptionDefault
iconNoEmoji, image URL, or local image path.
coverNoImage URL or local image path.
titleNo
blocksNo
parentYesParent database or page URL/id.
markdownNo
templateNoDatabase parents: "default", or a template name or id from notion_list_templates.
icon_emojiNoOlder name for icon.
propertiesNo
data_source_nameNo
allow_new_optionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/5.0
Behavior4/5

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

Annotations flag it as a non-idempotent, non-destructive, open-world write, and the description adds real behavior beyond that: properties are schema-validated, template applies a database template, and content can arrive as markdown or blocks. It doesn't mention auth/permission needs or what is created on failure, but the added context is substantive.

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?

Front-loads the core action, then orders clauses by parameter importance. Dense but every clause carries information; no filler sentences, though it is on the longer side.

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 11 parameters, nested block objects, no output schema, and 45% schema coverage, the description covers the branching logic and content formats an agent needs. Gaps remain around the return value and the unmentioned params (allow_new_options, data_source_name).

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 coverage is only 45%, so the description must carry weight and largely does: it explains parent (database vs page), properties validation, title filling, template, markdown/blocks, icon, and cover. It silently omits icon_emoji, data_source_name, and allow_new_options, so not fully compensating for the low coverage.

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?

States a specific verb+resource ('Create a page') and elaborates on the two creation modes (database parent vs page parent), which distinguishes it meaningfully from sibling reads like notion_get_page. It does not explicitly contrast itself with notion_duplicate_page or notion_bulk_create, so it lands at 4 rather than 5.

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

Usage Guidelines4/5

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

The description branches on parent type to explain what each mode does, and routes the agent to notion_update_properties, notion_list_templates, and notion_insert_blocks for adjacent semantics. It never states when to prefer this over siblings like notion_duplicate_page or notion_bulk_create, so no exclusions.

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

Deploy Server

Other Tools