Skip to main content
Glama

add_database_entry

Add a new entry to a Notion database by providing property values. Supports title, text, numbers, selects, dates, checkboxes, relations, and people.

Instructions

Create one database entry using simple key-value property inputs. Call get_database first to see available property names and valid select/status options.

Writable property values use simple inputs:

  • title, rich_text: string

  • number: number

  • select, status: option name string

  • multi_select: array of option name strings

  • date: ISO date string (start only)

  • checkbox: boolean

  • url, email, phone: string

  • relation: string or array of page IDs

  • people: string or array of user IDs

Not writable from this tool:

  • formula, rollup, unique_id, created_time, last_edited_time, created_by, last_edited_by: computed by Notion

  • files, verification, place, location, button: not supported for value writes here

Example: { "Name": "Buy groceries", "Status": "Todo", "Priority": "High", "Due": "2025-03-20", "Tags": ["Personal"] }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYesDatabase ID
propertiesYesKey-value property map to convert using the database schema
Behavior4/5

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

Without annotations, the description carries full responsibility for behavioral disclosure. It details the data types for writable properties and explicitly lists computed properties that cannot be written (e.g., formula, rollup). It implies creation is non-destructive to existing data but does not mention output, error handling, or permissions. Overall, it provides sufficient behavioral context for a creation tool.

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?

Every sentence in the description serves a purpose: first sentence states purpose and prerequisite, middle sections detail parameter syntax and limitations, final example consolidates instructions. The structure is logical and front-loaded, with 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?

The tool has two required parameters and no output schema. The description thoroughly explains input semantics and constraints, which is critical. However, it does not mention what the tool returns (e.g., the created entry ID), which would help the agent understand the side effect. Given the tool's simplicity, this is a minor gap.

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

Parameters5/5

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

The input schema has 100% description coverage but only basic descriptions (e.g., 'Database ID'). The description adds extensive value by specifying the exact format for each property type (string, number, select, etc.), including examples and an illustrative JSON object. This goes far beyond the schema, enabling correct parameter construction.

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 tool creates a single database entry using key-value properties. It distinguishes from the sibling 'add_database_entries' (plural) by specifying 'one entry'. It also provides a prerequisite action ('Call get_database first'), making the purpose unmistakable.

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?

The description explicitly instructs users to call 'get_database' to discover valid properties and options, which serves as clear guidance on when to use this tool. It lists unsupported property types, helping avoid misuse. However, it does not explicitly state when alternative tools like 'update_database_entry' might be preferred, though the context is implied.

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