Skip to main content
Glama
SunCreation

MCP Notion Server (@suncreation)

by SunCreation

notion_delete_block

Remove unwanted content blocks from Notion pages using block ID to maintain clean and organized workspaces.

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

  • Handler for notion_delete_block tool - validates block_id argument and calls notionClient.deleteBlock()
    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;
    }
  • Implementation of deleteBlock method in NotionClientWrapper - makes DELETE request to Notion API /blocks/{block_id} endpoint
    async deleteBlock(block_id: string): Promise<BlockResponse> {
      const response = await fetch(`${this.baseUrl}/blocks/${block_id}`, {
        method: "DELETE",
        headers: this.headers,
      });
    
      return response.json();
    }
  • Schema definition for notion_delete_block tool - defines name, description, and input schema with 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"],
      },
    };
  • Tool registration in ListToolsRequestSchema handler - adds deleteBlockTool to the list of available tools
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      const allTools = [
        schemas.appendBlockChildrenTool,
        schemas.retrieveBlockTool,
        schemas.retrieveBlockChildrenTool,
        schemas.deleteBlockTool,
        schemas.updateBlockTool,
        schemas.createPageTool,
        schemas.retrievePageTool,
        schemas.updatePagePropertiesTool,
        schemas.listAllUsersTool,
        schemas.retrieveUserTool,
        schemas.retrieveBotUserTool,
        schemas.createDatabaseTool,
        schemas.queryDatabaseTool,
        schemas.retrieveDatabaseTool,
        schemas.updateDatabaseTool,
        schemas.createDatabaseItemTool,
        schemas.createCommentTool,
        schemas.retrieveCommentsTool,
        schemas.searchTool,
      ];
      return {
        tools: filterTools(allTools, enabledToolsSet),
      };
    });
  • Type definition for DeleteBlockArgs interface - specifies block_id as string and optional format parameter
    export interface DeleteBlockArgs {
      block_id: string;
      format?: "json" | "markdown";
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete a block' implies a destructive mutation, but it doesn't mention permissions required, whether deletion is permanent/reversible, rate limits, or what happens to child blocks. For a destructive operation with zero annotation coverage, this is a significant gap in transparency.

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 a single, direct sentence with zero wasted words. It's perfectly front-loaded with the core action and resource, making it immediately scannable and efficient for an agent to parse.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion (success response, error conditions), doesn't mention permissions or side effects, and provides no usage context relative to sibling tools. The agent would struggle to use this tool correctly and safely.

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%, so the schema already fully documents both parameters (block_id format and format enum with usage guidance). The description adds no additional parameter information beyond what's in the schema, meeting the baseline expectation but not providing extra value.

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 target resource ('a block in Notion'), making the purpose immediately understandable. However, it doesn't differentiate this destructive operation from similar sibling tools like 'notion_update_block' or 'notion_retrieve_block', which would require explicit comparison to earn a 5.

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' (for modification) and 'notion_retrieve_block' (for reading), there's no indication of when deletion is appropriate versus updating or simply retrieving information. This leaves the agent without contextual decision-making help.

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/SunCreation/mcp-notion-server'

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