Skip to main content
Glama
SunCreation

MCP Notion Server (@suncreation)

by SunCreation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

notion_create_database_item

Add new pages to Notion databases by specifying database ID and property values. Supports JSON or markdown response formats for different use cases.

Instructions

Create a new item (page) in a Notion database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYesThe ID of the database to add the item to.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
propertiesYesProperties of the new database item. These should match the database schema.
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states the creation action without mentioning side effects, required permissions, rate limits, or consequences of invalid properties. The mutation intent is implied but not detailed.

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?

The description is a single concise sentence with no redundancy. However, it could be slightly improved by front-loading the key action and resource while being more structured.

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's complexity (3 parameters, nested object, no output schema), the description is incomplete. It does not mention the return value (the created page) or how to handle schema mismatches. The schema partially compensates but lacks behavioral context.

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?

Input schema has 100% description coverage, so the baseline is 3. The description adds no extra meaning beyond the schema; e.g., the format parameter's usage guidance is already in the schema. No new semantics are introduced.

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?

The description clearly states the action ('create') and the resource ('new item (page) in a Notion database'). It distinguishes from sibling tools like notion_create_database (creates whole database) and notion_update_page_properties (updates existing).

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 context is provided on when to use this tool versus alternatives, such as notion_update_page_properties for modifying existing items or notion_query_database for reading. No prerequisites or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools