Skip to main content
Glama

notion_create_database

Create a database in Notion to organize and structure information with customizable properties and rich text formatting.

Instructions

Create a database in Notion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parentYesParent object of the database
titleNoTitle of database as it appears in Notion. An array of rich text objects.
propertiesYesProperty schema of database. The keys are the names of properties as they appear in Notion and the values are property schema objects.
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

  • The core handler function in NotionClientWrapper that executes the tool by sending a POST request to Notion's /databases endpoint with parent, properties, and optional title.
    async createDatabase(
      parent: CreateDatabaseArgs["parent"],
      properties: Record<string, any>,
      title?: RichTextItemResponse[]
    ): Promise<DatabaseResponse> {
      const body = { parent, title, properties };
    
      const response = await fetch(`${this.baseUrl}/databases`, {
        method: "POST",
        headers: this.headers,
        body: JSON.stringify(body),
      });
    
      return response.json();
    }
  • Input schema definition for the notion_create_database tool, defining parameters like parent, title, properties.
    export const createDatabaseTool: Tool = {
      name: "notion_create_database",
      description: "Create a database in Notion",
      inputSchema: {
        type: "object",
        properties: {
          parent: {
            type: "object",
            description: "Parent object of the database",
          },
          title: {
            type: "array",
            description:
              "Title of database as it appears in Notion. An array of rich text objects.",
            items: richTextObjectSchema,
          },
          properties: {
            type: "object",
            description:
              "Property schema of database. The keys are the names of properties as they appear in Notion and the values are property schema objects.",
          },
          format: formatParameter,
        },
        required: ["parent", "properties"],
      },
    };
  • Registration and dispatch in the CallToolRequest handler switch statement, casting args and calling the client handler.
    case "notion_create_database": {
      const args = request.params
        .arguments as unknown as args.CreateDatabaseArgs;
      response = await notionClient.createDatabase(
        args.parent,
        args.properties,
        args.title
      );
      break;
    }
  • Tool is registered by including createDatabaseTool in the list returned by ListToolsRequest handler.
    schemas.createDatabaseTool,
  • TypeScript interface defining the arguments for createDatabase, used for type casting in the handler.
    export interface CreateDatabaseArgs {
      parent: {
        type: string;
        page_id?: string;
        database_id?: string;
        workspace?: boolean;
      };
      title?: RichTextItemResponse[];
      properties: Record<string, any>;
      format?: "json" | "markdown";
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It states 'Create' which implies a write/mutation operation, but doesn't mention required permissions, whether the operation is idempotent, rate limits, error conditions, or what happens on success (e.g., returns database ID). For a mutation tool with zero annotation coverage, this is inadequate.

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 wasted words. It's appropriately front-loaded with the core purpose. Every word earns its place, making it easy for an agent to parse quickly while scanning available tools.

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 this is a mutation tool (database creation) with no annotations, no output schema, and complex nested parameters, the description is insufficient. It doesn't explain what happens after creation (return value), error handling, authentication requirements, or provide context about the Notion database model. The agent would need to rely heavily on the input schema alone, which is inadequate for safe operation.

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 comprehensively documents all 4 parameters (parent, title, properties, format) with detailed descriptions and constraints. The description adds no additional parameter information beyond what's in the schema, which is acceptable given the high schema coverage but doesn't provide any helpful context about how parameters interact or typical usage patterns.

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 ('database in Notion'), making the purpose immediately understandable. It distinguishes from siblings like 'notion_create_database_item' (which creates items within databases) and 'notion_update_database' (which modifies existing databases), though it doesn't explicitly mention these distinctions in the description text itself.

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 a parent page), compare with similar tools like 'notion_update_database' for modifications, or indicate when database creation is appropriate versus using existing databases. The agent must infer usage from the name alone.

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