Skip to main content
Glama
Sign In
notion-mcp

notion-mcp

by snickery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

notion_replace_page_content

Replaces a Notion page's entire content with new Markdown, overwriting all existing blocks. Use it for full-page rewrites; for targeted edits, use the content update tool instead.

Instructions

Replace a page's entire content with new markdown.

Overwrites all existing content. Use notion_read_page_markdown first to see what's there. For targeted edits, use notion_update_page_content instead.

page_id: the page to replace content on. markdown: new page content in markdown format. allow_deleting_content: must be True when the replacement would delete a child page or database that is on the page now. markdown_version: "v2" treats markdown as Notion-flavored Markdown (a preview syntax); default is the stable syntax.

Very large pages are processed by Notion as a background task; if it is still running when this returns, the reply carries a task ID for notion_get_async_task.

Input Schema

NameRequiredDescriptionDefault
page_idYes
markdownYes
markdown_versionNo
allow_deleting_contentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / allow_deleting_content
      Added value: +{
+  "default": false,
+  "title": "Allow Deleting Content",
+  "type": "boolean"
+}
    • addedInput schema / properties / markdown_version
      Added value: +{
+  "default": "",
+  "title": "Markdown Version",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does: it declares the overwrite/destructive semantics, the guard condition for allow_deleting_content when child pages or databases would be destroyed, and the preview-vs-stable markdown tradeoff. It also discloses that very large pages run as a background task and return a task ID for notion_get_async_task, which is non-obvious operational behavior an agent must plan for.

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?

Front-loaded with the action and the destructive warning, then per-parameter notes, then the async caveat in order of operational importance. No filler sentences; each block conveys distinct information.

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?

An output schema exists so return values need not be explained, yet the description still flags the async task-ID case that changes what the agent should do next. Given a 4-parameter destructive tool with no annotations, this covers everything needed to invoke it safely.

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 description coverage is 0%, so the description must supply all meaning and it documents all four parameters, including the conditional requirement on allow_deleting_content and the meaning of "v2" for markdown_version. Minor gap: page_id is described only vaguely (no indication of whether an ID, URL, or slug is accepted) and markdown's format expectations are thin.

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?

States a specific verb and resource plus scope: "Replace a page's entire content with new markdown." The word "entire" immediately separates it from partial-edit siblings like notion_update_page_content and notion_insert_page_content.

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

Usage Guidelines5/5

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

Gives explicit prerequisites ("Use notion_read_page_markdown first to see what's there") and an explicit alternative ("For targeted edits, use notion_update_page_content instead"). When-to-use, when-not-to-use, and the sibling to route to are all present.

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