Skip to main content
Glama
Sjotie

Notion MCP Server

by Sjotie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create-page

Add a new page to a Notion database with custom properties and optional content blocks.

Instructions

Create a new page in a database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_idYesID of the parent database
propertiesYesPage properties
childrenNoOptional content blocks

Implementation Reference

  • server.js:377-399 (handler)
    The execution handler for the 'create-page' tool. It extracts parameters from the request, constructs the page creation payload, calls the Notion API to create the page, and returns the response as text content.
    else if (name === "create-page") {
  const { parent_id, properties, children } = args;
  
  const pageParams = {
    parent: { database_id: parent_id },
    properties,
  };

  if (children) {
    pageParams.children = children;
  }

  const response = await notion.pages.create(pageParams);

  return {
    content: [
      {
        type: "text",
        text: JSON.stringify(response, null, 2),
      },
    ],
  };
}
  • server.js:83-104 (registration)
    Registration of the 'create-page' tool in the tools/list endpoint, defining its name, description, and input schema for validation.
    {
  name: "create-page",
  description: "Create a new page in a database",
  inputSchema: {
    type: "object",
    properties: {
      parent_id: {
        type: "string",
        description: "ID of the parent database"
      },
      properties: {
        type: "object",
        description: "Page properties"
      },
      children: {
        type: "array",
        description: "Optional content blocks"
      }
    },
    required: ["parent_id", "properties"]
  }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool creates a page, implying a write operation, but does not address permissions, side effects, error conditions, or response format. This is a significant gap for a mutation tool with no annotation coverage.

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 a single, clear sentence with no wasted words. It is appropriately sized and front-loaded, efficiently conveying the core purpose without unnecessary elaboration.

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?

Given the complexity of a creation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., what happens on success/failure) and does not compensate for the absence of structured output information, making it inadequate for full agent understanding.

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 (children, parent_id, properties). The description adds no additional meaning beyond the schema, such as examples or constraints, but since the schema is comprehensive, the baseline score of 3 is appropriate.

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 the action ('Create') and the resource ('new page in a database'), making the purpose evident. However, it does not differentiate this tool from potential siblings like 'create-database' or 'update-page', which would require specifying that this creates a page within an existing database rather than a database itself.

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. It does not mention prerequisites (e.g., needing a parent database ID), exclusions, or comparisons to siblings like 'append-block-children' or 'update-page', leaving the agent to infer usage context.

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