notion-mcp-server

update-page

Update a Notion page's properties, icon, cover, archive status, or lock status with partial updates. Set icon or cover to null to remove; archive to trash or lock to prevent edits.

Instructions

Update a Notion page's properties, icon, cover, archive status, or lock status. Partial updates are supported - only provide the fields you want to change. Set icon or cover to null to remove them. Set archived to true to move the page to trash. Set is_locked to true to lock the page in the UI. Returns updated page ID and URL.

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": {
      "page_id": "<page_id>"
    },
    "name": "update-page"
  }
}

Input Schema

Name	Required	Description
`page_id`	Yes	Page ID
`properties`	No	Properties object
`archived`	No	Archive status
`icon`	No	Icon { type: "emoji", emoji: "📝" } or { type: "external", external: { url: "..." } }
`cover`	No	Cover image { type: "external", external: { url: "..." } }
`is_locked`	No	Lock to prevent UI edits

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.14.0May 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Without annotations, the description carries full burden. It discloses key behaviors: partial updates, removal of icon/cover via null, archiving, locking, and return of page ID and URL. It does not mention permissions or side effects on other properties, but the partial update behavior is clearly stated.

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?

The description is 4 sentences, each conveying essential information without redundancy. It front-loads the purpose, then covers partial updates, specific field behaviors, and return value. No extraneous text.

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 6 parameters, nested objects (icon, cover), and no output schema, the description covers main behaviors and return value. It could elaborate on the 'properties' object format (e.g., Notion property value structure) and potential side effects, but overall sufficiently complete.

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% but description adds significant meaning: explains use of null for removal, boolean effects (archive, lock), and the concept of partial updates. It goes beyond schema descriptions, which are minimal for 'properties'.

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?

Description clearly states the tool updates a Notion page's properties, icon, cover, archive status, or lock status. It specifically names the resource (page) and the actions (update properties, set icon/cover, archive, lock), distinguishing it from sibling tools like 'update-block' or 'archive-page'.

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 explains partial updates and provides examples of when to set certain fields (e.g., null to remove, true to archive/lock). However, it does not explicitly contrast with sibling tools like 'archive-page' or 'update-block', leaving ambiguous which tool to use for block-level vs. page-level updates.

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