Skip to main content
Glama
Notion MCP Server

Notion MCP Server

notion_update_page

Update an existing Notion page by ID, including changing its title or appending new content, to keep workspace pages current.

Instructions

Update an existing Notion page

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": "notion_update_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew page title (optional)
pageIdYesThe ID of the page to update
contentNoNew content to append (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about mutability semantics, permission requirements, failure modes for nonexistent pages, or whether omitted fields are preserved. Critically, the "content" parameter appends rather than replaces content, a behavior the description never states.

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?

The single short sentence is front-loaded and contains no filler, but it is terse to the point of underspecification rather than genuinely economical given the tool's mutation semantics.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description should explain what happens to existing page content and what a successful response looks like. It leaves both unaddressed, so an agent cannot confidently predict the tool's effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters (pageId, title, content) are already documented in the schema, establishing the baseline of 3. The description adds no additional meaning about parameter interaction or formatting beyond what the schema provides.

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

Purpose3/5

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

The description names a specific verb and resource ("Update an existing Notion page"), which distinguishes it from notion_create_page, notion_get_page, and notion_archive_page by name alone. However, it doesn't say which fields can be changed or how it differs from notion_append_blocks, which overlaps with the "content" parameter.

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?

There is no guidance on when to use this tool versus notion_append_blocks or notion_create_page, no prerequisite information (permissions, page existence), and no statement about what should not be done with it. The agent must infer everything from the tool name.

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