Skip to main content
Glama

create_database

Create a Notion database under a parent page with a custom schema supporting multiple property types like text, number, select, date, and relations.

Instructions

Create a database under a parent page.

Supported property types and extras:

  • title

  • rich_text (alias: text)

  • number (optional: format, for example "dollar", "percent", "number_with_commas")

  • select, multi_select, status (optional: options array of strings or {name, color, description})

  • date, checkbox, url, email, phone

  • formula (required: expression, for example "prop("Count") * 2")

  • rollup (required: function, relation_property, rollup_property)

  • relation (required: data_source_id; optional: relation_type "single_property" or "dual_property", synced_property_name)

  • unique_id (optional: prefix, for example "ENG")

  • people, files

  • created_time, last_edited_time, created_by, last_edited_by

  • verification, place, location, button

Unknown property types fail with an explicit error. No silent drops.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesDatabase title
parent_page_idYesParent page ID
schemaYesArray of {name, type} property definitions
is_inlineNoCreate the database inline within the parent page
Behavior4/5

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

No annotations provided, so description carries full burden. It explicitly mentions error handling ('Unknown property types fail with an explicit error. No silent drops') and details optional configurations per property type. Lacks info on auth, quotas, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured: opens with purpose, then lists property types in clear shorthand, ends with error note. Length appropriate for complexity, no filler.

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

Completeness4/5

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

Covers property types thoroughly, but does not mention return value (no output schema) or constraints on parent_page_id (e.g., valid page). Still, for a creation tool with many options, it is fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, baseline 3. Description adds significant value beyond schema by detailing supported property types and their extra fields (e.g., format, options, expression).

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?

Clearly states 'Create a database under a parent page' and lists supported property types. Differentiates from sibling tools like create_page by specifying database creation.

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 when-to-use or alternatives described. Many sibling tools for different operations (e.g., create_page, add_database_entries) but no guidance on choosing this one.

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/Grey-Iris/easy-notion-mcp'

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