Skip to main content
Glama
Sign In
Notion Advisor

Notion Advisor

by m2ai-mcp-servers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_block

Archive a block to remove unwanted content from a Notion page. Provide the block ID to delete it and keep your workspace organized.

Instructions

Delete a block (archive it). Use when user wants to remove content from a 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": {
      "block_id": "<block_id>"
    },
    "name": "delete_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_idYesBlock ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that deletion is actually archiving, which prevents an agent from promising permanent deletion. However, it does not explain consequences such as what happens to child blocks, whether the operation is reversible, or what response to expect.

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?

Two short sentences deliver the action, the archival nuance, and the primary use case. There is no filler or redundant information.

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 single-parameter tool with no output schema, the description covers the core behavior and the triggering user intent. It omits minor details like response shape or error behavior, but an agent has enough information to invoke it correctly in most cases.

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?

Schema description coverage is 100%, and the only parameter block_id is already described as 'Block ID to delete.' The description adds no additional context about where the block ID comes from or its format, but the schema fully documents the parameter.

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 states a specific action and object: 'Delete a block (archive it).' The parenthetical 'archive it' clarifies the exact semantic, and 'remove content from a page' distinguishes this from sibling tools like append_blocks or update_block.

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 explicitly says when to use the tool: 'Use when user wants to remove content from a page.' It doesn't mention alternatives or exclusion criteria, but the usage context is clear and unambiguous.

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