notion-mcp-server

replace-page-content

Replace all page content with Markdown. Preserves child databases and pages. Non-Markdown blocks are deleted; use dry run to preview deletions.

Instructions

Replace all page content with Markdown. Preserves child_database/child_page only. WARNING: Non-Markdown blocks (bookmark, callout, equation, etc.) will be DELETED. Use dry_run: true to preview deletions. For partial updates, use find-and-replace-in-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": {
      "page_id": "<page_id>",
      "content": "<content>"
    },
    "name": "replace-page-content"
  }
}

Input Schema

Name	Required	Description
`page_id`	Yes	Page ID
`content`	Yes	Content in Markdown
`dry_run`	No	Preview mode: shows which blocks will be deleted without actually modifying the page (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.14.0May 27, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations provided, the description fully discloses the destructive behavior: non-Markdown blocks will be deleted. It also warns and suggests a preview. While additional details like authentication requirements or rate limits are missing, the disclosure is sufficient for safe operation.

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?

Three sentences, each serving a distinct purpose: purpose, warning, and alternative. Highly concise and front-loaded, with no wasted words.

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?

Given the simple parameter set (3 params, no nested objects, no output schema) and the presence of sibling tools indicating alternatives, the description covers all necessary guidance: what the tool does, its destructive nature, how to preview, and when to use an alternative. The agent can make an informed decision.

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 the description adds meaning beyond the schema: it clarifies that 'content' must be Markdown and explains the effect of using it, and highlights that 'dry_run' previews deletions. This enriches the agent's understanding of how parameters affect behavior.

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?

The description clearly states the action ('Replace all page content') and the resource ('with Markdown'), and distinguishes from sibling tools by specifying it replaces all content and preserves only child_database/child_page. This gives the agent a precise understanding of the tool's function.

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?

Explicitly provides when to use ('replace all page content with Markdown'), when not to use (for partial updates, 'use find-and-replace-in-page'), and a safety mechanism ('Use dry_run: true to preview deletions'). This guides correct invocation and prevents misuse.

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