Skip to main content
Glama

notion_delete_block

Remove unwanted content from Notion pages by deleting specific blocks using their unique ID. Choose JSON format for programmatic access or Markdown for readability.

Instructions

Delete a block in Notion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesThe ID of the block to delete.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
formatNoSpecify the response format. 'json' returns the original data structure, 'markdown' returns a more readable format. Use 'markdown' when the user only needs to read the page and isn't planning to write or modify it. Use 'json' when the user needs to read the page with the intention of writing to or modifying it.markdown

Implementation Reference

  • The core handler function in NotionClientWrapper that executes the DELETE request to the Notion API endpoint /blocks/{block_id} to delete the block.
    async deleteBlock(block_id: string): Promise<BlockResponse> {
      const response = await fetch(`${this.baseUrl}/blocks/${block_id}`, {
        method: "DELETE",
        headers: this.headers,
      });
    
      return response.json();
    }
  • The tool dispatch handler in the MCP server's CallToolRequest handler that validates the input arguments and calls the NotionClientWrapper's deleteBlock method.
    case "notion_delete_block": {
      const args = request.params
        .arguments as unknown as args.DeleteBlockArgs;
      if (!args.block_id) {
        throw new Error("Missing required argument: block_id");
      }
      response = await notionClient.deleteBlock(args.block_id);
      break;
    }
  • The schema definition for the 'notion_delete_block' tool, including name, description, and input schema specifying the required 'block_id' parameter.
    export const deleteBlockTool: Tool = {
      name: "notion_delete_block",
      description: "Delete a block in Notion",
      inputSchema: {
        type: "object",
        properties: {
          block_id: {
            type: "string",
            description: "The ID of the block to delete." + commonIdDescription,
          },
          format: formatParameter,
        },
        required: ["block_id"],
      },
    };
  • Registration of the deleteBlockTool schema in the array of available tools returned by the ListToolsRequest handler.
    schemas.deleteBlockTool,
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete' clearly indicates a destructive operation, the description doesn't mention important behavioral aspects: whether deletion is permanent or reversible, what permissions are required, whether child blocks are also deleted, or what happens to the response. The format parameter description adds some behavioral context about output formats, but doesn't compensate for the core behavioral gaps.

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 perfectly concise at just 5 words, front-loading the core purpose without unnecessary elaboration. Every word earns its place, and there's no wasted text. The structure is straightforward and immediately communicates the essential action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive operation with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical contextual information: what happens after deletion (confirmation? error handling?), whether the operation is idempotent, what permissions are needed, or what the response contains. The format parameter adds some context but doesn't compensate for the broader gaps in understanding this mutation tool's behavior.

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 100% schema description coverage, the schema already documents both parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema. The baseline score of 3 reflects adequate parameter documentation through the schema alone, though the description doesn't enhance understanding of when or why to use specific parameter values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete') and resource ('a block in Notion'), making the purpose immediately understandable. However, it doesn't differentiate this destructive operation from sibling tools like notion_update_block or notion_retrieve_block, which would help the agent understand the tool's specific role in the Notion API ecosystem.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like notion_update_block (which can modify blocks) and notion_retrieve_block (which reads blocks), there's no indication of when deletion is appropriate versus modification or retrieval. The format parameter description offers some usage guidance for that specific parameter, but not for the tool as a whole.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kimjungyeol/mcp-notion-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server