Skip to main content
Glama
Hermoso

Hermoso

Official

Update a Notion database row

update_notion_row
DestructiveIdempotent

Update one Notion database row's properties by column name, such as status, URL, or date, with validation before sending. Also moves a row to trash or restores it.

Instructions

Change properties on ONE row of a Notion database (pageId from query_notion_database) — e.g. mark a calendar row Status "Posted" and put the live post link in its URL column. properties is {"Column": value} by column name: text, number, checkbox, select (an existing option or a new one), status (must be an existing option), multi-select (array; replaces the whole value), date (ISO, or {start, end}), url, email, phone; null clears. Validated against the database's own columns before anything is sent and refused by name otherwise, never coerced; columns you do not name keep their values. Read back from Notion. trash:true moves the row to Notion's trash (restorable; returns a preview first and needs confirm:true), trash:false restores it. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pageId": "<pageId>"
    },
    "name": "update_notion_row"
  }
}

Input Schema

NameRequiredDescriptionDefault
trashNotrue moves the row to Notion trash (needs confirm); false restores it
pageIdYesthe row id or link
confirmNotrue confirms moving the row to trash; not needed for other changes
propertiesNo{"Column": value}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.465

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: values are validated against the database's own columns and refused by name rather than coerced, unnamed columns are preserved, results are read back from Notion, and trash is described as restorable and preview-then-confirm. That last point is the key context for a tool annotated destructiveHint=true — the agent learns the destructive action is reversible and gated.

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?

Front-loads the core action and example, then layers type rules and trash behavior, with no filler sentences. The type enumeration is a dense semicolon chain that reads more like a reference dump than prose, which costs it a point but not its efficiency.

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

Completeness5/5

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

For a 4-param mutation tool with no output schema, everything an agent needs is present: accepted value shapes, validation and refusal behavior, preservation of unnamed columns, and the two-step trash/confirm flow. Return behavior is summarized as 'read back from Notion,' which suffices without an output schema.

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?

Schema coverage is 100%, so baseline would be 3, but the description substantially enriches it: per-type value formats (text, number, checkbox, select new-or-existing, status existing-only, multi-select array that replaces the whole value, ISO date or {start, end}, url/email/phone), null-to-clear semantics, and confirm:true being required only for trashing. The schema's bare {"Column": value} and boolean hints would leave an agent guessing without this.

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?

Names a specific verb and resource (change properties on ONE row of a Notion database) and scopes it to a single page, which cleanly separates it from append_to_notion_page and query_notion_database. The concrete example (marking a calendar row Status "Posted" with a live post link) makes the intended job 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?

Tells the agent where pageId comes from (query_notion_database) and clearly bifurcates the two modes: property edits via properties, versus trash:true/false with confirm:true. It does not explicitly say what to use instead for adding page content, so the sibling routing is implied rather than stated.

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