Skip to main content
Glama

update_data_source

Update a Notion database schema by renaming, adding, updating, or removing properties, changing the title, or moving to/from trash. Must resend full option lists for select/status fields.

Instructions

CRITICAL: full-list semantics. When you update a select or status property's options array, you MUST send the full desired list. Any existing option you omit will be permanently removed from the database, along with any relationship to rows currently using it. Rows that currently reference a removed option are silently reassigned to the default group's first option (for example "Not started" for status properties). No signal is raised. If you want to preserve the meaning of existing rows when removing an option, reclassify those rows to another explicit option before removing the option from the schema. To add one option, first call get_database, then resend the full current list with your addition appended.

Cannot toggle is_inline on existing databases. is_inline is a database-level field, not a data-source field. A separate update_database tool may be added later.

Updates a database's schema: rename properties, add or update property definitions, remove properties, change the title, or move it to/from trash. Use after get_database. Supports raw Notion payloads and schema helper payloads; read resource easy-notion://docs/update-data-source for modes, examples, status notes, and limitations. At least one of title, properties, or in_trash must be provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYesDatabase ID
titleNoNew database title
propertiesNoRaw Notion property update map
in_trashNoTrue to trash, false to restore
Behavior5/5

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

With no annotations provided, the description carries full burden and excels by disclosing a critical side effect: full-list semantics for select/status options, leading to permanent removal and silent reassignment of rows. It also notes the inability to toggle is_inline on existing databases. These details prevent surprise behavior.

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

Conciseness3/5

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

The description is verbose but front-loaded with the critical warning. It contains multiple paragraphs with some redundancies (e.g., listing actions twice). While the information is valuable, it could be more streamlined to reduce length without sacrificing clarity.

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?

Given no output schema, the description omits return values, which is a minor gap. It covers purpose, constraints, and behavioral warnings well. The reference to an external resource for payload modes may limit completeness for agents without resource access, but the main points are sufficiently addressed.

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 coverage is 100%, so baseline is 3. The description adds value by explaining that the properties parameter is a 'Raw Notion property update map', references resource for details, and clarifies that at least one of title, properties, or in_trash must be provided. This enriches the basic schema descriptions.

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 'Updates a database's schema' and enumerates specific actions: rename properties, add/update/remove properties, change title, move to/from trash. It distinguishes this from siblings like create_database and get_database by its update focus and full-list semantics warning. The is_inline constraint further clarifies scope.

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 'Use after get_database' and provides a concrete scenario for adding an option. It explicitly states that is_inline cannot be toggled here, implying a different tool would be needed. However, it does not explicitly enumerate when not to use this tool or list alternatives beyond the mentioned constraint.

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