Skip to main content
Glama
awkoy

notion-mcp-server

create_page

Generate a new page in Notion with customizable properties, optional content blocks, and settings for icons or cover images using JSON schema inputs.

Instructions

Create a new page in Notion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
childrenNoOptional array of paragraph blocks to add as page content
coverNoOptional cover image for the page
iconNoOptional icon for the page
parentNoOptional parent - if not provided, will use NOTION_PAGE_ID as parent page
propertiesYesProperties of the page

Implementation Reference

  • The core handler function that implements the 'create_page' tool logic. It invokes the Notion API to create a new page with the given parameters and returns a success message with the page ID or handles errors.
    export const registerCreatePageTool = async (
      params: CreatePageParams
    ): Promise<CallToolResult> => {
      try {
        const response = await notion.pages.create(params);
    
        return {
          content: [
            {
              type: "text",
              text: `Page created successfully: ${response.id}`,
            },
          ],
        };
      } catch (error) {
        return handleNotionError(error);
      }
    };
  • Defines the Zod schema (CREATE_PAGE_SCHEMA) used for validating input parameters to the create_page operation, including parent, properties, children, icon, and cover.
    export const CREATE_PAGE_SCHEMA = {
      parent: PARENT_SCHEMA.optional()
        .default({
          type: "page_id",
          page_id: getRootPageId(),
        })
        .describe(
          "Optional parent - if not provided, will use NOTION_PAGE_ID as parent page"
        ),
      properties: z
        .record(
          z.string().describe("Property name"),
          z.union([
            TITLE_PROPERTY_SCHEMA,
            CHECKBOX_PROPERTY_VALUE_SCHEMA,
            EMAIL_PROPERTY_VALUE_SCHEMA,
            STATUS_PROPERTY_VALUE_SCHEMA,
            FILES_PROPERTY_VALUE_SCHEMA,
            DATE_PROPERTY_VALUE_SCHEMA,
            PEOPLE_PROPERTY_VALUE_SCHEMA,
            PHONE_NUMBER_PROPERTY_VALUE_SCHEMA,
            RELATION_PROPERTY_VALUE_SCHEMA,
            RICH_TEXT_PROPERTY_VALUE_SCHEMA,
            SELECT_PROPERTY_VALUE_SCHEMA,
            NUMBER_PROPERTY_VALUE_SCHEMA,
          ])
        )
        .describe("Properties of the page"),
      children: z
        .array(TEXT_BLOCK_REQUEST_SCHEMA)
        .optional()
        .describe("Optional array of paragraph blocks to add as page content"),
      icon: z.preprocess(
        preprocessJson,
        ICON_SCHEMA.nullable().optional().describe("Optional icon for the page")
      ),
      cover: z.preprocess(
        preprocessJson,
        FILE_SCHEMA.nullable()
          .optional()
          .describe("Optional cover image for the page")
      ),
    };
  • Registers the 'notion_pages' MCP tool, which encompasses the 'create_page' action (along with others) using PAGES_OPERATION_SCHEMA and the dispatcher handler.
      "notion_pages",
      "Perform various page operations (create, archive, restore, search, update)",
      PAGES_OPERATION_SCHEMA,
      registerPagesOperationTool
    );
  • Dispatcher logic in the 'notion_pages' tool handler that routes 'create_page' action calls to the specific registerCreatePageTool implementation.
    case "create_page":
      return registerCreatePageTool(params.payload.params);
  • Part of PAGES_OPERATION_SCHEMA discriminated union defining the structure for 'create_page' action including its literal discriminator and params schema.
      action: z
        .literal("create_page")
        .describe("Use this action to create a new page in the database."),
      params: z.object(CREATE_PAGE_SCHEMA),
    }),
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 'Create a new page' which implies a write operation, but it does not disclose any behavioral traits such as required permissions, whether the operation is idempotent, rate limits, or what happens on failure. This is a significant gap for a mutation tool with zero 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, efficient sentence with zero waste: 'Create a new page in Notion'. It is appropriately sized and front-loaded, clearly stating the core action 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 (5 parameters with nested objects, no annotations, no output schema), the description is incomplete. It does not address behavioral aspects like mutation effects, error handling, or return values, nor does it provide usage context. For a tool with rich input schema but no other structured data, the description should do more to guide the agent.

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 schema description coverage is 100%, so the schema already documents all parameters (e.g., 'children', 'cover', 'icon', 'parent', 'properties') in detail. The description adds no meaning beyond what the schema provides, as it does not explain parameter usage, relationships, or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Create a new page in Notion' clearly states the verb ('Create') and resource ('page in Notion'), making the purpose immediately understandable. However, it does not distinguish this tool from potential siblings like 'append_block_children' or 'batch_mixed_operations', which might also involve page creation or modification, so it lacks sibling differentiation.

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., parent page/database requirements), when not to use it (e.g., for updating existing pages), or refer to sibling tools like 'update_block' or 'archive_page' for related operations.

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

Related 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/awkoy/notion-mcp-server'

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