Skip to main content
Glama

create_page

Add new entries like tasks, projects, or notes to Notion databases by setting properties such as title, status, date, and assignee.

Instructions

Creates a new page (record) in a Notion database. Use this to add new entries such as tasks, projects, notes, etc. to any database. You can set properties like title, status, date, assignee, and more when creating the page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
databaseIdYesThe ID of the Notion database where the page will be created (32 or 36 character UUID format). Example: "123e4567-e89b-12d3-a456-426614174000"
propertiesYesProperties to set for the new page. Use property names as keys and provide values according to property types. The format is the same as update_page. Example (creating a task): { "Name": { "title": [{ "text": { "content": "Write weekly report" } }] }, "Status": { "select": { "name": "TODO" } }, "Priority": { "select": { "name": "High" } }, "Due Date": { "date": { "start": "2024-12-31" } } }

Implementation Reference

  • Tool registration for 'create_page' in the MCP server's getTools() method, including name, description, and detailed input schema.
          {
            name: 'create_page',
            description: 'Creates a new page (record) in a Notion database. Use this to add new entries such as tasks, projects, notes, etc. to any database. You can set properties like title, status, date, assignee, and more when creating the page.',
            inputSchema: {
              type: 'object',
              properties: {
                databaseId: {
                  type: 'string',
                  description: 'The ID of the Notion database where the page will be created (32 or 36 character UUID format). Example: "123e4567-e89b-12d3-a456-426614174000"',
                },
                properties: {
                  type: 'object',
                  description: `Properties to set for the new page. Use property names as keys and provide values according to property types. The format is the same as update_page.
    
    Example (creating a task):
    {
      "Name": { "title": [{ "text": { "content": "Write weekly report" } }] },
      "Status": { "select": { "name": "TODO" } },
      "Priority": { "select": { "name": "High" } },
      "Due Date": { "date": { "start": "2024-12-31" } }
    }`,
                },
              },
              required: ['databaseId', 'properties'],
            },
          },
  • MCP tool handler for 'create_page'. Dispatches from the CallToolRequestSchema handler, executes the CreatePageUseCase, and formats the response as MCP content.
    private async handleCreatePage(args: any) {
      const result = await this.dependencies.createPageUseCase.execute({
        databaseId: args.databaseId,
        properties: args.properties,
      });
    
      return {
        content: [
          {
            type: 'text' as const,
            text: JSON.stringify(
              {
                id: result.id.toString(),
                properties: result.properties,
                createdTime: result.createdTime,
                lastEditedTime: result.lastEditedTime,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Core business logic handler implementing page creation via repository interaction.
    export class CreatePageUseCase {
      constructor(private readonly pageRepository: IPageRepository) {}
    
      async execute(input: CreatePageInput): Promise<Page> {
        const databaseId = new DatabaseId(input.databaseId);
        return await this.pageRepository.create(databaseId, input.properties);
      }
    }
  • Type definition for input to CreatePageUseCase, matching the MCP tool schema.
    export interface CreatePageInput {
      databaseId: string;
      properties: PageProperties;
    }
Behavior3/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 correctly indicates this is a write operation ('Creates'), but does not mention permissions required, rate limits, whether the operation is idempotent, or what happens on failure. It adds some context about what can be set (properties like title, status, etc.), but lacks comprehensive behavioral details.

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 appropriately sized with three sentences that are front-loaded and efficient. The first sentence states the core purpose, the second provides usage context, and the third adds parameter context—each sentence earns its place without redundancy or unnecessary elaboration.

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

Completeness3/5

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

Given the tool's complexity (write operation with nested objects), no annotations, and no output schema, the description is moderately complete but has gaps. It covers the basic purpose and parameter context, but lacks details on permissions, error handling, return values, or behavioral constraints that would be needed for full contextual 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 fully documents both parameters (databaseId and properties). The description adds marginal value by mentioning property examples (title, status, date, assignee) and linking to update_page format, but does not provide significant additional semantics beyond what the schema already specifies.

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 specific action ('Creates a new page'), resource ('in a Notion database'), and scope ('add new entries such as tasks, projects, notes, etc.'). It distinguishes from siblings like delete_page (deletion), get_page (retrieval), and update_page (modification) by focusing on creation of new records.

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 provides clear context for when to use this tool ('to add new entries such as tasks, projects, notes, etc. to any database'), but does not explicitly state when not to use it or name specific alternatives. It implies usage for creation vs. update_page for modifications, but lacks explicit exclusions or comparisons.

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/Kazy1014/notion-mcp'

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