Skip to main content
Glama
SunCreation

MCP Notion Server (@suncreation)

by SunCreation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

notion_update_page_properties

Modify properties of Notion pages or database items by specifying page ID and property updates to change fields like status, dates, or tags.

Instructions

Update properties of a page or an item in a Notion database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesThe ID of the page or database item to update.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
propertiesYesProperties to update. These correspond to the columns or fields in the database.
formatNoSpecify the response format. 'json' returns the original data structure, 'markdown' returns a more readable format. Use 'markdown' when the user only needs to read the page and isn't planning to write or modify it. Use 'json' when the user needs to read the page with the intention of writing to or modifying it.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It states 'update' implying mutation, but does not mention authentication requirements, rate limits, side effects, or whether the operation is reversible. This is insufficient for an update operation.

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?

Description is a single sentence, concise and to the point. However, it omits some behavioral details that could be included without making it verbose.

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?

Given that there is no output schema, the description does not clarify what is returned after update (e.g., the updated page object). It partially covers input via parameter semantics, but overall completeness is moderate, especially considering the complexity of updating Notion properties.

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%, baseline is 3. The description adds useful context: 'properties' are likened to database columns/fields. The 'format' parameter includes explicit guidance on when to use each enum value (markdown vs json), which adds significant semantic value beyond the 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?

Description clearly states the verb (update) and resource (properties of a page/database item). However, it does not differentiate from sibling tools like notion_update_block or notion_update_database, which also perform updates on different resources.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions. The description simply states the action without any usage advice.

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