Skip to main content
Glama
cphoskins
by cphoskins

create_page

Create a new Notion page under a parent page or database, specifying title, optional emoji icon, content blocks, and database properties.

Instructions

Create a new Notion page under a parent page or database.

Args: parent_id: ID of the parent page or database. title: Title for the new page. parent_type: "page_id" (default) or "database_id". icon_emoji: Optional emoji character to use as the page icon. children_json: Optional JSON array of block objects for initial content. properties_json: Optional JSON object of additional database properties to set. Example for setting Status: {"Status": {"status": {"name": "Done"}}} Example for setting Date: {"Due date": {"date": {"start": "2026-04-15"}}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_idYes
titleYes
parent_typeNopage_id
icon_emojiNo
children_jsonNo
properties_jsonNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It mentions creating a page and lists optional parameters, but does not disclose behavioral traits such as required permissions, rate limits, or what happens if the parent does not exist. The description is adequate but not thorough.

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 concise and well-structured, with a clear opening sentence followed by a bulleted list of parameters. Every sentence adds necessary information without redundancy.

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

Completeness5/5

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

Given the complexity of 6 parameters and no schema descriptions, the description covers all parameters meaningfully, including examples for the most complex one. It provides sufficient information for an AI agent to select and invoke the tool correctly.

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?

With 0% schema description coverage, the description adds value by explaining each parameter (e.g., parent_id is ID, parent_type defaults to page_id) and provides explicit examples for properties_json, which the schema lacks. This compensates well for the schema gaps.

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 verb 'Create', the resource 'page', and the context 'under a parent page or database'. It is specific and distinguishes the tool from siblings that perform different actions like appending blocks or updating pages.

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?

The description provides no guidance on when to use this tool versus alternatives like 'copy_page_to_parent' or 'update_page'. It does not mention prerequisites, limitations, or when another tool would be more appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cphoskins/notion-full-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server