Skip to main content
Glama

Create Database

notion_create_database

Create a new Notion database with initial property schema and data source.

Instructions

Create a Notion database and its initial data source. Use this when the user wants a new database. For Notion API 2025-09-03+, put the initial schema under initial_data_source.properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconNoOptional Notion icon object for the database.
coverNoOptional Notion cover object for the database.
titleNoTitle of the database as an array of rich text 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.
parentYesParent page or workspace object for the new database, for example { type: 'page_id', page_id: '...' }.
is_inlineNoWhether the database should be displayed inline in the parent page. Defaults to false.
descriptionNoDescription of the database as an array of rich text objects.
initial_data_sourceYesInitial data source configuration. Provide properties here, not as a top-level database property.
Behavior3/5

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

Annotations already indicate this is not read-only, not idempotent, not destructive. Description adds a minor behavioral detail about API version but does not disclose return value, atomicity, or success/failure conditions. Given annotations cover basic traits, a 3 is appropriate.

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?

Two sentences with no wasted words. First sentence states purpose; second sentence adds version-specific guidance. Front-loaded and efficiently structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 8 parameters and no output schema. The description is minimal and does not mention return value (e.g., the created database object) or explain the relationship between initial_data_source and top-level properties. Adequate but leaves gaps for an agent unfamiliar with Notion API.

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 coverage is 100% with descriptions for all 8 parameters. The description only adds a small note about initial_data_source.properties for API 2025-09-03+, which is a useful nuance but not significant beyond what the schema already provides.

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

Purpose5/5

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

Description clearly states the verb 'Create' and the resource 'Notion database and its initial data source'. It also explicitly says 'Use this when the user wants a new database', making the purpose unmistakable and differentiating it from siblings like notion_create_data_source.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear usage scenario ('when the user wants a new database') and includes a version-specific note about API 2025-09-03+. Does not explicitly exclude alternatives or mention when not to use, but the guidance is sufficient for correct invocation.

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