Skip to main content
Glama

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

  • 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"]
      }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a creation operation, implying mutation, but doesn't cover critical aspects like required permissions, whether the operation is idempotent, error handling, or what happens on success (e.g., returns a page ID). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, achieving optimal conciseness for such a basic description.

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 tool's complexity (3 parameters with nested objects, no output schema, and no annotations), the description is inadequate. It doesn't explain what 'properties' or 'children' entail in practice, what the tool returns, or any behavioral constraints. For a creation tool with multiple parameters and no structured support, more context is needed to be complete.

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?

The description adds no parameter-specific information beyond what the schema provides. Since schema description coverage is 100%, the baseline score is 3. The schema already documents 'parent_id' as the database ID, 'properties' as page properties, and 'children' as optional content blocks, so the description doesn't enhance parameter understanding.

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 resource ('new page in a database'), making the tool's purpose immediately understandable. It distinguishes itself from siblings like 'create-database' (which creates databases rather than pages) and 'append-block-children' (which adds to existing pages). However, it doesn't specify what kind of database or platform this refers to, which keeps it from being fully specific.

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 doesn't mention prerequisites (e.g., needing an existing database), exclusions (e.g., not for updating pages), or comparisons to siblings like 'update-page' for modifications or 'create-database' for creating databases instead of pages. This leaves the agent with minimal context for tool selection.

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/Sjotie/notionMCP'

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