Skip to main content
Glama
Selenium39

Qiita API MCP Server

delete_item

Remove articles from the Qiita developer community platform by specifying the article ID to manage content effectively.

Instructions

指定された記事を削除します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes記事ID

Implementation Reference

  • The MCP tool handler for 'delete_item'. It validates input with itemIdSchema and executes by calling QiitaApiClient.deleteItem with the itemId.
    delete_item: {
      schema: itemIdSchema,
      execute: async ({ itemId }, client) => client.deleteItem(itemId),
    },
  • The tool definition schema for 'delete_item' provided in the ListTools response, including name, description, and input schema.
      name: 'delete_item',
      description: '指定された記事を削除します',
      inputSchema: {
        type: 'object',
        properties: {
          itemId: {
            type: 'string',
            description: '記事ID',
          },
        },
        required: ['itemId'],
      },
    },
  • Core helper function in QiitaApiClient that authenticates and performs the HTTP DELETE request to the Qiita API endpoint `/items/${itemId}`.
    async deleteItem(itemId: string) {
      this.assertAuthenticated();
      const response = await this.client.delete(`/items/${itemId}`);
      return response.data;
    }
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. While '削除します' clearly indicates a destructive operation, it doesn't specify whether deletion is permanent/reversible, what permissions are required, whether it cascades to related data (comments/stocks), or what confirmation/response to expect. For a destructive tool with zero annotation coverage, this is inadequate.

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 Japanese sentence that directly states the tool's function without any unnecessary words. It's perfectly front-loaded with the core action and resource, making it immediately comprehensible.

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 operation tool with no annotations and no output schema, the description is insufficient. It doesn't address critical context like authentication requirements, error conditions, what happens to associated data (comments/stocks), or what the tool returns upon success/failure. Given the complexity and risk of deletion operations, more completeness is needed.

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 description doesn't add any parameter information beyond what's already in the schema (100% coverage). The schema fully documents the single required 'itemId' parameter with its Japanese description '記事ID' (article ID). The description's mention of '指定された記事' (specified article) aligns with but doesn't expand upon the schema.

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 ('削除します' - deletes) and the resource ('指定された記事' - specified article), making the purpose immediately understandable. It doesn't specifically differentiate from sibling tools like 'delete_comment' or 'unstock_item', but the resource type (article vs comment/stock) provides implicit distinction.

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_item' for modification or 'get_item' for viewing. There's no mention of prerequisites (authentication needs), consequences, or appropriate contexts for deletion versus other operations on articles.

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