Skip to main content
Glama

delete_page

Archive Notion pages to organize completed tasks and finished projects. Deleted pages can be restored later for flexible content management.

Instructions

Deletes (archives) a Notion page (database record). In Notion, deletion is actually an archive operation and can be restored later. Use this to organize completed tasks, finished projects, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIdYesThe ID of the Notion page to delete (archive). Must be 32 or 36 character UUID format. Example: "123e4567-e89b-12d3-a456-426614174000"

Implementation Reference

  • Registration of the 'delete_page' tool in the MCP server's tool list, including name, description, and input schema.
    {
      name: 'delete_page',
      description: 'Deletes (archives) a Notion page (database record). In Notion, deletion is actually an archive operation and can be restored later. Use this to organize completed tasks, finished projects, etc.',
      inputSchema: {
        type: 'object',
        properties: {
          pageId: {
            type: 'string',
            description: 'The ID of the Notion page to delete (archive). Must be 32 or 36 character UUID format. Example: "123e4567-e89b-12d3-a456-426614174000"',
          },
        },
        required: ['pageId'],
      },
    },
  • MCP server handler for 'delete_page' tool invocations, delegates to DeletePageUseCase and returns success response.
    private async handleDeletePage(args: any) {
      await this.dependencies.deletePageUseCase.execute({
        pageId: args.pageId,
      });
    
      return {
        content: [
          {
            type: 'text' as const,
            text: 'Page deleted successfully',
          },
        ],
      };
    }
  • Type definition for input to the delete page use case.
    export interface DeletePageInput {
      pageId: string;
    }
  • Core business logic handler in DeletePageUseCase that performs the page deletion via repository.
    async execute(input: DeletePageInput): Promise<void> {
      const pageId = new PageId(input.pageId);
      await this.pageRepository.delete(pageId);
    }
Behavior5/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. It effectively explains that deletion is actually an archive operation in Notion, can be restored later, and implies it's a destructive action (though reversible), adding crucial context beyond basic functionality.

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 front-loaded with the core action and key behavioral details in the first sentence, followed by a practical usage example. Every sentence adds value without redundancy, making it efficient and well-structured for quick understanding.

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 destructive tool with no annotations and no output schema, the description does well by explaining the archive behavior and reversibility. However, it could improve by mentioning permissions or side effects, but given the simplicity (one parameter) and clear behavioral context, it is largely complete.

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?

The schema description coverage is 100%, with the parameter 'pageId' fully documented in the input schema. The description does not add any additional meaning or details about the parameter beyond what the schema provides, so it meets the baseline for high schema coverage without extra value.

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 specific action ('Deletes (archives) a Notion page') and resource ('page (database record)'), distinguishing it from siblings like update_page or get_page. It provides precise terminology about Notion's archive behavior, making the purpose unambiguous.

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 includes explicit usage context ('Use this to organize completed tasks, finished projects, etc.'), which helps guide when to apply the tool. However, it does not specify when to use alternatives like update_page for modifications or explicitly state exclusions, leaving some room for improvement in sibling differentiation.

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

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