Skip to main content
Glama
Sign In
notion-private-api-mcp

notion-private-api-mcp

by kirvigen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Delete Blocks

delete_blocks

Remove and archive specified child blocks from a page, keeping content recoverable while decluttering the workspace.

Instructions

Remove direct child blocks from a page and archive those 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>",
      "block_ids": "<block_ids>"
    },
    "name": "delete_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesParent page id or page URL.
block_idsYesBlock ids or block URLs to remove from the page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden. It discloses that blocks are archived, adding some behavioral context, but does not mention permissions, irreversibility, or side effects on the page.

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?

A single concise sentence that directly states the tool's action and result. No unnecessary words.

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?

For a simple tool with two well-described parameters and no output schema, the description covers the core functionality adequately. It could mention error conditions or return values, but it is complete enough for the tool's complexity.

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%, so baseline is 3. The description adds that blocks are 'direct child blocks', providing context beyond the schema's description of block IDs. This extra detail enhances parameter understanding.

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 tool removes direct child blocks from a page and archives them, using specific verbs and resource. It distinguishes from sibling tools like append_blocks and update_block_text which perform different operations.

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 guidelines are provided for when to use this tool versus alternatives. There is no mention of prerequisites, scenarios, or when not to use it.

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