mcp-notion-fast

Delete block

delete_block

DestructiveIdempotent

Move a Notion block to trash by providing its block ID. This destructive action permanently removes the block from your workspace.

Instructions

Move a Notion block to trash. This is a destructive operation.

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": {
      "blockId": "<blockId>"
    },
    "name": "delete_block"
  }
}

Input Schema

Name	Required	Description	Default
`blockId`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`code`	No
`data`	No
`error`	No
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds the specific behavior of moving to trash (soft delete) rather than permanent deletion, which goes beyond the bare 'destructive' annotation and provides useful context about reversibility.

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?

The description is two short sentences, front-loaded with the action and immediately followed by a critical warning. Every word contributes to understanding, with no redundancy or filler.

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 one-parameter deletion tool with annotations and an output schema, the description covers the core behavior (move to trash) and destructive nature. It lacks explicit prerequisites or edge-case behavior, but overall it is sufficiently complete for an AI agent to select and invoke it correctly.

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?

With 0% schema description coverage, the description should compensate, but it does not mention the blockId parameter. However, the single parameter's name is self-explanatory, and the schema requires only a string blockId, so the meaning is inferable. The description adds no explicit parameter detail.

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 ('Move a Notion block to trash') with a specific verb and resource, distinguishing it from sibling tools like get_block, update_block, and append_block_children. It unambiguously identifies this as the deletion operation.

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?

The description implies usage for deleting a block and warns that it is destructive, providing clear context. It does not explicitly name alternatives or state when not to use it, but the verb 'Move to trash' makes the intended scenario obvious.

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

Deploy Server