Skip to main content
Glama

notion_create_database_item

Add new pages to Notion databases by specifying database ID and properties that match the 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 implementation of the notion_create_database_item tool. Makes a POST request to Notion's /pages endpoint to create a new page (item) 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();
    }
  • Input schema definition for the notion_create_database_item tool, defining parameters like database_id and properties.
    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"],
      },
    };
  • Registration and dispatching of the notion_create_database_item tool in the MCP server's CallToolRequest handler switch statement.
    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;
    }
  • Tool registration in the list of allTools for ListToolsRequest response.
    schemas.createDatabaseItemTool,
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. It mentions it's a creation operation, implying mutation, but lacks details on permissions required, error handling, rate limits, or what happens on success/failure. For a write tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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 zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without redundancy or fluff.

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, including nested objects, with no output schema and no annotations), the description is incomplete. It doesn't address behavioral aspects like permissions or errors, and while the schema covers parameters, the overall context for safe and effective use is lacking. For a mutation tool, this is inadequate.

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 clarify 'properties' mapping or 'database_id' format). Baseline 3 is appropriate when the schema does the heavy lifting, but the description doesn't compensate or 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 a new item') and resource ('in a Notion database'), specifying it's a page. It distinguishes from siblings like 'notion_create_database' (creates a database) and 'notion_update_page_properties' (updates existing pages), but doesn't explicitly contrast with all siblings. The purpose is specific and unambiguous.

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 explicit guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over similar tools like 'notion_create_database' or 'notion_update_page_properties', nor does it provide context about prerequisites or typical use cases. The description only states what it does, not when to use it.

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

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