Skip to main content
Glama
microcmsio

microCMS MCP Server

by microcmsio

microcms_delete_content

Delete content from microCMS by specifying the content type and content ID to remove specific items from your CMS database.

Instructions

Delete content from microCMS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointYesContent type name (e.g., "blogs", "news")
contentIdYesContent ID to delete

Implementation Reference

  • The main handler function that executes the tool logic: validates input and calls the deleteContent helper from client.ts.
    export async function handleDeleteContent(params: ToolParameters) {
      const { endpoint, contentId } = params;
      
      if (!contentId) {
        throw new Error('contentId is required');
      }
    
      await deleteContent(endpoint, contentId);
      return { message: `Content ${contentId} deleted successfully` };
    }
  • Tool definition with name, description, and input schema for parameter validation.
    export const deleteContentTool: Tool = {
      name: 'microcms_delete_content',
      description: 'Delete content from microCMS',
      inputSchema: {
        type: 'object',
        properties: {
          endpoint: {
            type: 'string',
            description: 'Content type name (e.g., "blogs", "news")',
          },
          contentId: {
            type: 'string',
            description: 'Content ID to delete',
          },
        },
        required: ['endpoint', 'contentId'],
      },
    };
  • src/server.ts:121-123 (registration)
    Registration in the server CallToolRequest handler: switch case dispatches to the tool handler.
    case 'microcms_delete_content':
      result = await handleDeleteContent(params);
      break;
  • src/server.ts:49-72 (registration)
    Registration in ListToolsRequest handler: deleteContentTool is included in the tools list (line 63).
        tools: [
          getListTool,
          getListMetaTool,
          getContentTool,
          getContentMetaTool,
          createContentPublishedTool,
          createContentDraftTool,
          createContentsBulkPublishedTool,
          createContentsBulkDraftTool,
          updateContentPublishedTool,
          updateContentDraftTool,
          patchContentTool,
          patchContentStatusTool,
          patchContentCreatedByTool,
          deleteContentTool,
          getMediaTool,
          uploadMediaTool,
          deleteMediaTool,
          getApiInfoTool,
          getApiListTool,
          getMemberTool,
        ],
      };
    });
  • Supporting utility that performs the actual microCMS API deletion call using the SDK client.
    export async function deleteContent(
      endpoint: string,
      contentId: string
    ): Promise<void> {
      return await microCMSClient.delete({
        endpoint,
        contentId,
      });
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the action ('Delete') without behavioral details. It doesn't disclose if deletion is permanent, requires specific permissions, has side effects, or what happens on success/failure. This is inadequate for a destructive operation with zero annotation coverage.

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, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 tool with no annotations and no output schema, the description is incomplete. It lacks critical context like deletion behavior, permissions, error handling, or return values. Given the complexity and risk of deletion, more detail is needed to guide the agent effectively.

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 parameters 'endpoint' and 'contentId' are fully documented in the schema. The description adds no additional meaning beyond the schema, such as examples or constraints. Baseline 3 is appropriate when the schema handles all parameter documentation.

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

Purpose3/5

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

The description 'Delete content from microCMS' states a clear verb ('Delete') and resource ('content'), but it's vague about scope and doesn't differentiate from sibling tools like 'microcms_delete_media'. It doesn't specify what type of content or deletion behavior, making it minimally adequate but lacking specificity.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, when not to use it, or compare to siblings like 'microcms_patch_content_status' for status changes. The agent must infer usage from context alone.

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/microcmsio/microcms-mcp-server'

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