Skip to main content
Glama
Selenium39

Qiita API MCP Server

delete_comment

Remove unwanted or outdated comments from Qiita articles to maintain content quality and relevance. Specify the comment ID to delete specific comments.

Instructions

指定されたコメントを削除します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commentIdYesコメントID

Implementation Reference

  • The handler for the 'delete_comment' tool. It defines the input schema using commentIdSchema and the execute function that calls the QiitaApiClient's deleteComment method with the provided commentId.
    delete_comment: {
      schema: commentIdSchema,
      execute: async ({ commentId }, client) => client.deleteComment(commentId),
    },
  • The MCP tool registration for 'delete_comment', including name, description, and input schema definition.
    {
      name: 'delete_comment',
      description: '指定されたコメントを削除します',
      inputSchema: {
        type: 'object',
        properties: {
          commentId: {
            type: 'string',
            description: 'コメントID',
          },
        },
        required: ['commentId'],
      },
    },
  • The Zod schema definition for commentId input, used by the delete_comment handler.
    const commentIdSchema = z.object({
      commentId: z.string(),
    });
  • The QiitaApiClient helper method that implements the actual DELETE request to the Qiita API to delete the comment.
    async deleteComment(commentId: string) {
      this.assertAuthenticated();
      await this.client.delete(`/comments/${commentId}`);
      return { success: true };
    }
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. It only states the action ('delete') without details on side effects (e.g., if it's destructive, requires confirmation, affects related data), error handling, or response format. For a mutation tool with zero annotation coverage, this is insufficient.

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, clear sentence in Japanese that directly states the tool's action without unnecessary words. It's front-loaded and efficiently conveys the core purpose, making it highly concise and well-structured.

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?

Given the tool's complexity as a destructive operation with no annotations and no output schema, the description is incomplete. It lacks critical context such as behavioral traits (e.g., permanence, permissions), error cases, or what happens post-deletion, which is essential for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description doesn't add parameter semantics beyond the input schema, which has 100% coverage and clearly documents the single required 'commentId' parameter. With only one parameter fully described in the schema, the baseline is high even without extra details in the description.

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 states the action ('削除します' - delete) and target ('コメント' - comment), which clarifies the tool's basic purpose. However, it doesn't differentiate from sibling tools like 'delete_item' or specify what type of comment system this is (e.g., blog, forum, document). The purpose is clear but lacks specificity about scope or context.

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 like 'update_comment' or prerequisites such as authentication. It doesn't mention if deletion is permanent, reversible, or requires specific permissions, leaving the agent with no usage context beyond the basic action.

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/Selenium39/mcp-server-qiita'

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