notion-mcp-server

clear-page-content

Delete all content from a Notion page. Optionally preserve child databases and pages, or clear everything by setting preserve types to empty.

Instructions

Delete all content from a page. By default, preserves child_database and child_page blocks. Use preserve_types=[] to delete everything. For deleting specific blocks, use delete-blocks-batch instead. Blocks are deleted sequentially to respect API rate limits (3 req/s). Returns count of deleted blocks.

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>"
    },
    "name": "clear-page-content"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes	Page ID
`preserve_types`	No	Block types to preserve (default: ["child_database", "child_page"]). Set to empty array [] to delete all.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.14.0May 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Discloses sequential deletion to respect API rate limits (3 req/s) and returns count of deleted blocks. No annotations exist, so description carries full behavioral burden. Could mention permissions but adequate.

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 purposeful: states purpose, default behavior with alternative, and behavioral detail with return info. No redundancy.

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 two params, no annotations, no output schema, description covers purpose, usage, behavior, and return value. Could mention reversibility or limits but sufficient for simple tool.

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 has 100% description coverage, so baseline 3. Description adds default value behavior for preserve_types and suggests empty array to delete all, adding value beyond schema.

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?

Description clearly states 'Delete all content from a page' and contrasts with sibling tool 'delete-blocks-batch' for deleting specific blocks. Verb and resource are explicit.

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

Usage Guidelines4/5

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

Explicitly states default preservation behavior and how to delete everything (use preserve_types=[]). Also directs to sibling tool for specific block deletion. No exclusions but clear when to use.

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