Skip to main content
Glama
Sign In
notion-mcp

notion-mcp

by snickery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

notion_update_page

Update a Notion page's title, icon, or properties by page ID. Change only the fields you specify, optionally skip notifications, and leave all other properties unchanged.

Instructions

Update a Notion page's title, icon, or other properties.

page_id: the page to update. title: new title (leave empty to keep current). properties_json: JSON object of properties to update. Keys are property names, values are Notion API property value objects. Omitted properties are left unchanged. Wiki verification is a property too: {"Verification": {"verification": {"state": "verified"}}}. icon: "remove" to clear it, or an emoji, "custom_emoji:", "icon:[:]" (native Notion icon) or an image URL. silent: True skips the update, @mention and Person-property notifications this write would send.

Input Schema

NameRequiredDescriptionDefault
iconNo
titleNo
silentNo
page_idYes
properties_jsonNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / silent
      Added value: +{
+  "default": false,
+  "title": "Silent",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that this is a write operation and that silent=True skips update, @mention, and Person-property notifications. It does not discuss permissions, whether updates are reversible, or error behavior, which are meaningful gaps for an unannotated mutation 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?

The description is front-loaded with the primary action and then uses a compact parameter list. Every line contributes specific operational detail, and there is no redundant explanation of fields already clear from the schema. The structure supports quick scanning.

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 five parameters, 0% schema description coverage, and an output schema, the description covers all input semantics well. It is nearly complete for invocation, though it omits auth or permission expectations and basic failure modes that an agent might need in edge cases.

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 description coverage is 0%, and the description compensates by documenting every parameter. It explains the properties_json shape with a concrete Wiki verification example and gives detailed icon syntax including remove, emoji, custom emoji, native icon, and URL forms. This is materially more informative than the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: "Update a Notion page's title, icon, or other properties." That is clear enough for an agent to know it mutates page metadata rather than page content. It does not explicitly differentiate from nearby siblings like notion_update_page_content or notion_set_page_visual, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides parameter-level guidance, such as leaving title empty to keep the current title and omitting properties to leave them unchanged. However, it does not explicitly say when to choose this tool over notion_update_page_content, notion_set_page_visual, or notion_update_block. Usage is implied rather than explicitly directed.

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