Skip to main content
Glama
Selenium39

Qiita API MCP Server

unstock_item

Remove an article from your Qiita stock list by providing its article ID to manage your saved content.

Instructions

指定された記事のストックを解除します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes記事ID

Implementation Reference

  • Handler definition for the 'unstock_item' tool. It validates input using itemIdSchema and delegates execution to the QiitaApiClient's unstockItem method.
    unstock_item: {
      schema: itemIdSchema,
      execute: async ({ itemId }, client) => client.unstockItem(itemId),
    },
  • MCP tool schema definition for 'unstock_item', including name, description, and input schema requiring 'itemId'.
    {
      name: 'unstock_item',
      description: '指定された記事のストックを解除します',
      inputSchema: {
        type: 'object',
        properties: {
          itemId: {
            type: 'string',
            description: '記事ID',
          },
        },
        required: ['itemId'],
      },
    },
  • Core helper method in QiitaApiClient that authenticates and sends DELETE request to Qiita API endpoint to unstock the specified item.
    async unstockItem(itemId: string) {
      this.assertAuthenticated();
      await this.client.delete(`/items/${itemId}/stock`);
      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 states the action ('unstock') but doesn't clarify if this is a destructive operation, requires authentication, has side effects, or what the expected outcome is. This leaves significant gaps for an agent to understand the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized for a simple operation, though it could be slightly more informative without losing conciseness.

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 lack of annotations and output schema, the description is insufficiently complete. It doesn't explain what 'unstocking' entails (e.g., removal from a list, toggling a state), potential errors, or return values, leaving the agent with incomplete context for a mutation tool.

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 'itemId' clearly documented as 'article ID'. The description doesn't add any extra meaning beyond this, but since the schema is comprehensive, a baseline score of 3 is appropriate as it doesn't need to compensate for gaps.

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 ('unstock') and resource ('article'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'stock_item' or 'is_item_stocked' beyond the basic verb difference, missing explicit scope or relationship 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?

No guidance is provided on when to use this tool versus alternatives such as 'stock_item' or 'delete_item', nor does it mention prerequisites like requiring the item to be stocked first. The description is purely functional without contextual usage advice.

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