Skip to main content
Glama

ghost_delete_page

Permanently removes a page from Ghost CMS using its unique ID, with no undo.

Instructions

Deletes a page from Ghost CMS by ID. This operation is permanent and cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the page to delete.

Implementation Reference

  • The tool handler registered for 'ghost_delete_page'. Calls ghostService.deletePage(id), logs success, and returns a confirmation text response.
      withErrorHandling('ghost_delete_page', deletePageSchema, async (input) => {
        const { id } = input;
        await ghostService.deletePage(id);
        mcpLogger.info(`Page deleted successfully. Page ID: ${id}`);
    
        return {
          content: [{ type: 'text', text: `Page ${id} has been successfully deleted.` }],
        };
      })
    );
  • Registration of the 'ghost_delete_page' tool via server.registerTool with description, inputSchema, and the async handler.
    server.registerTool(
      'ghost_delete_page',
      {
        description:
          'Deletes a page from Ghost CMS by ID. This operation is permanent and cannot be undone.',
        inputSchema: deletePageSchema,
      },
      withErrorHandling('ghost_delete_page', deletePageSchema, async (input) => {
        const { id } = input;
        await ghostService.deletePage(id);
        mcpLogger.info(`Page deleted successfully. Page ID: ${id}`);
    
        return {
          content: [{ type: 'text', text: `Page ${id} has been successfully deleted.` }],
        };
      })
    );
  • Input schema (Zod object) for the delete page tool: requires 'id' (validated via ghostIdSchema).
    const deletePageSchema = z.object({
      id: ghostIdSchema.meta({ description: 'The ID of the page to delete.' }),
    });
  • The deletePage export from pages service, which is an alias for service.remove (generated by createResourceService factory).
    export const deletePage = service.remove;
  • The remove function in the resource service factory that calls deleteResource (from ghostApiClient) with the resource name, id, and label.
    async function remove(id) {
      return deleteResource(resource, id, label);
    }
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explicitly notes that the operation is permanent and irreversible, which is a critical behavioral trait beyond a simple delete. However, it could mention required permissions or side effects.

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, direct sentences with no filler. The key information is front-loaded.

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 delete tool with one required parameter and no output schema, the description covers the essential functionality and the irreversible nature. However, it lacks details about success/error responses or any required permissions.

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 already explains the 'id' parameter. The description does not add new meaning beyond the schema, so it meets the baseline with no 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 action (deletes), resource (page from Ghost CMS), and identifier (by ID). It differentiates from sibling tools like ghost_delete_post or ghost_delete_tag by specifying 'page'.

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?

No guidance on when to use this tool versus alternatives such as ghost_delete_post or ghost_delete_tag. No mention of prerequisites or conditions for use.

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/jgardner04/Ghost-MCP-Server'

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