Skip to main content
Glama
Sjotie

Notion MCP Server

by Sjotie
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

create-database

Create a new database in Notion by specifying parent page, title, and property schema to organize information and structure content.

Instructions

Create a new database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_idYesID of the parent page
titleYesDatabase title as rich text array
propertiesYesDatabase properties schema
iconNoOptional icon for the database
coverNoOptional cover for the database

Implementation Reference

  • server.js:425-462 (handler)
    Handler for the 'create-database' tool. Processes arguments, sanitizes parent_id, constructs database creation parameters, handles optional icon and cover with default emoji fallback, calls Notion API to create database, and returns the response as formatted JSON text.
    else if (name === "create-database") {
  let { parent_id, title, properties, icon, cover } = args;
  
  // Remove dashes if present in parent_id
  parent_id = parent_id.replace(/-/g, "");

  const databaseParams = {
    parent: {
      type: "page_id",
      page_id: parent_id,
    },
    title,
    properties,
  };

  // Set default emoji if icon is specified but emoji is empty
  if (icon && icon.type === "emoji" && !icon.emoji) {
    icon.emoji = "📄"; // Default document emoji
    databaseParams.icon = icon;
  } else if (icon) {
    databaseParams.icon = icon;
  }

  if (cover) {
    databaseParams.cover = cover;
  }

  const response = await notion.databases.create(databaseParams);

  return {
    content: [
      {
        type: "text",
        text: JSON.stringify(response, null, 2),
      },
    ],
  };
}
  • server.js:130-155 (schema)
    Input schema definition for the 'create-database' tool, specifying required parent_id, title, properties, and optional icon/cover.
    inputSchema: {
  type: "object",
  properties: {
    parent_id: {
      type: "string",
      description: "ID of the parent page"
    },
    title: {
      type: "array",
      description: "Database title as rich text array"
    },
    properties: {
      type: "object",
      description: "Database properties schema"
    },
    icon: {
      type: "object",
      description: "Optional icon for the database"
    },
    cover: {
      type: "object",
      description: "Optional cover for the database"
    }
  },
  required: ["parent_id", "title", "properties"]
}
  • server.js:127-156 (registration)
    Tool registration entry in the MCP server's tools list/array, defining name, description, and input schema for 'create-database'.
    {
  name: "create-database",
  description: "Create a new database",
  inputSchema: {
    type: "object",
    properties: {
      parent_id: {
        type: "string",
        description: "ID of the parent page"
      },
      title: {
        type: "array",
        description: "Database title as rich text array"
      },
      properties: {
        type: "object",
        description: "Database properties schema"
      },
      icon: {
        type: "object",
        description: "Optional icon for the database"
      },
      cover: {
        type: "object",
        description: "Optional cover for the database"
      }
    },
    required: ["parent_id", "title", "properties"]
  }
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Create a new database' implies a write operation but doesn't specify permissions needed, whether this is idempotent, what happens on failure, or any rate limits. For a creation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 front-loaded with the core action and resource, making it immediately scannable and appropriately sized for the tool's complexity.

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 creates a database (a complex operation with 5 parameters including nested objects), no annotations, and no output schema, the description is insufficient. It doesn't address what the tool returns, error conditions, or how it interacts with sibling tools like 'list-databases' or 'update-database'. More context is needed for effective use.

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 parameters are well-documented in the schema itself. The description adds no additional parameter context beyond the basic action, which meets the baseline for high schema coverage. However, it doesn't explain relationships between parameters (e.g., how 'parent_id' relates to 'title') or provide usage examples.

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 'Create a new database' clearly states the verb ('Create') and resource ('database'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create-page' or 'update-database', which would require more specificity about what distinguishes database creation from page creation or database updates.

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. With siblings like 'create-page', 'list-databases', and 'update-database', there's no indication of prerequisites, appropriate contexts, or when other tools might be more suitable. The user must infer usage from the tool 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/Sjotie/notionMCP'

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