Skip to main content
Glama

update_database_entry

Update an existing Notion database entry by providing only the properties to change. Use simple key-value inputs for titles, numbers, selects, dates, and more.

Instructions

Update an existing database entry using simple key-value property inputs. Pass only properties to change; omitted properties are left unchanged. Call get_database first to see available property names and valid select/status options.

Writable property values use the same simple inputs as add_database_entry:

  • 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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesPage ID for the database entry
propertiesYesKey-value property map to convert using the parent database schema
Behavior4/5

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

With no annotations, the description details which property types are writable and lists those that are computed or unsupported, such as 'formula, rollup, unique_id, etc.' It explains that omitted properties are left unchanged, but does not mention return value, auth, or error behavior.

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 well-structured, front-loading the core purpose and usage strategy. It lists writable and non-writable types concisely without redundancy. Minor verbosity could be trimmed, but each sentence adds distinct value.

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 description covers the input format and constraints well, but lacks information on the return value or success/failure indicators (no output schema). It also does not mention error handling, idempotency, or permissions, which are important for a non-trivial update tool.

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 schema has 100% coverage with descriptions, but the description adds crucial details: the format of values for each property type (string, number, date, etc.), and clarifies that properties is a key-value map. This goes beyond the schema's minimal explanation.

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 specifies the verb 'Update' and the resource 'database entry' using key-value property inputs. It distinguishes from sibling tools like add_database_entry (add) and delete_database_entry (delete) by focusing on modification of existing entries.

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 advises calling get_database first to 'see available property names and valid select/status options,' providing clear context for correct usage. It also states to pass only changed properties, but does not explicitly exclude alternatives like update_page.

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