Skip to main content
Glama

notion_create_database

Create a database in Notion to organize information, track projects, or manage data within your workspace.

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

  • Core handler function that executes the Notion API call to create a database.
    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();
    }
  • Tool dispatch handler that parses arguments and calls the Notion client.
    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 schema defining input validation and description for notion_create_database.
    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"],
      },
    };
  • Registers the notion_create_database tool (as schemas.createDatabaseTool) in the list 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 but offers minimal information. It states 'Create' which implies a write/mutation operation, but doesn't mention required permissions, whether this is an irreversible action, rate limits, or what happens on success/failure. The description adds no context beyond the basic verb.

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 maximally concise at just 4 words with zero wasted language. It's front-loaded with the core action and resource, though this brevity comes at the cost of completeness. Every word earns its place in conveying the basic purpose.

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 inadequate. It doesn't explain what a successful creation returns, error conditions, or behavioral nuances. While the schema covers parameters well, the description fails to provide the broader context needed for safe and effective tool invocation in a complex system like Notion.

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 description provides no parameter information, but the input schema has 100% description coverage with detailed documentation for all 4 parameters (parent, title, properties, format). The schema thoroughly explains each parameter's purpose, structure, and constraints, so the baseline score of 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a database in Notion' is essentially a tautology that restates the tool name 'notion_create_database' without adding meaningful specificity. It doesn't distinguish this tool from sibling tools like 'notion_create_database_item' (which creates items within a database) or clarify what 'database' means in the Notion context beyond the obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 it to similar tools like 'notion_update_database' for modifications, or indicate when database creation is appropriate versus other Notion 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

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