Skip to main content
Glama

notion_create_database_item

Add new pages to Notion databases by specifying database ID and property values that match the existing schema.

Instructions

Create a new item (page) in a Notion database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYesThe ID of the database to add the item to.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
propertiesYesProperties of the new database item. These should match the database schema.
formatNoSpecify the response format. 'json' returns the original data structure, 'markdown' returns a more readable format. Use 'markdown' when the user only needs to read the page and isn't planning to write or modify it. Use 'json' when the user needs to read the page with the intention of writing to or modifying it.markdown

Implementation Reference

  • Core handler function that executes the tool logic by making a POST request to the Notion API `/pages` endpoint to create a new item (page) in the specified database.
    async createDatabaseItem(
      database_id: string,
      properties: Record<string, any>
    ): Promise<PageResponse> {
      const body = {
        parent: { database_id },
        properties,
      };
    
      const response = await fetch(`${this.baseUrl}/pages`, {
        method: "POST",
        headers: this.headers,
        body: JSON.stringify(body),
      });
    
      return response.json();
    }
  • Server-side dispatcher that handles incoming CallToolRequest for this tool and delegates to the NotionClientWrapper.
    case "notion_create_database_item": {
      const args = request.params
        .arguments as unknown as args.CreateDatabaseItemArgs;
      response = await notionClient.createDatabaseItem(
        args.database_id,
        args.properties
      );
      break;
  • Defines the tool schema including name, description, and input validation schema.
    export const createDatabaseItemTool: Tool = {
      name: "notion_create_database_item",
      description: "Create a new item (page) in a Notion database",
      inputSchema: {
        type: "object",
        properties: {
          database_id: {
            type: "string",
            description:
              "The ID of the database to add the item to." + commonIdDescription,
          },
          properties: {
            type: "object",
            description:
              "Properties of the new database item. These should match the database schema.",
          },
          format: formatParameter,
        },
        required: ["database_id", "properties"],
      },
    };
  • Registers the tool in the ListToolsRequest handler by including it in the array of available tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      const allTools = [
        schemas.appendBlockChildrenTool,
        schemas.retrieveBlockTool,
        schemas.retrieveBlockChildrenTool,
        schemas.deleteBlockTool,
        schemas.updateBlockTool,
        schemas.retrievePageTool,
        schemas.updatePagePropertiesTool,
        schemas.listAllUsersTool,
        schemas.retrieveUserTool,
        schemas.retrieveBotUserTool,
        schemas.createDatabaseTool,
        schemas.queryDatabaseTool,
        schemas.retrieveDatabaseTool,
        schemas.updateDatabaseTool,
        schemas.createDatabaseItemTool,
        schemas.createCommentTool,
        schemas.retrieveCommentsTool,
        schemas.searchTool,
      ];
      return {
        tools: filterTools(allTools, enabledToolsSet),
      };
    });
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 it creates a new item, implying a write operation, but doesn't cover permissions required, rate limits, error conditions, or what the response looks like (since no output schema exists). This leaves significant gaps for a mutation tool.

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 and wastes no space, making it easy for an agent to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral details (e.g., auth needs, side effects), usage context, and output information, leaving the agent under-informed despite the clear purpose and concise structure.

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 fully documents all parameters. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain property mapping or format implications further), meeting the baseline for high schema coverage.

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 a new item') and resource ('in a Notion database'), specifying it creates a page. It distinguishes from siblings like notion_create_database (creates databases) and notion_update_page_properties (modifies existing pages), though it doesn't explicitly name these alternatives.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a database ID), exclusions, or compare with similar tools like notion_create_database or notion_update_page_properties, 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.

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

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