Skip to main content
Glama
Selenium39

Qiita API MCP Server

stock_item

Save articles to your Qiita reading list for later reference by providing the article ID.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes記事ID

Implementation Reference

  • Handler for the 'stock_item' MCP tool. Validates the input using itemIdSchema and executes by calling the Qiita client's stockItem method.
    stock_item: {
      schema: itemIdSchema,
      execute: async ({ itemId }, client) => client.stockItem(itemId),
    },
  • MCP tool definition for 'stock_item', including name, description, and input schema requiring 'itemId'.
    {
      name: 'stock_item',
      description: '指定された記事をストックします',
      inputSchema: {
        type: 'object',
        properties: {
          itemId: {
            type: 'string',
            description: '記事ID',
          },
        },
        required: ['itemId'],
      },
    },
  • Core implementation in QiitaApiClient that authenticates and makes PUT request to Qiita API to stock the specified item.
    async stockItem(itemId: string) {
      this.assertAuthenticated();
      await this.client.put(`/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 ('stocks') but doesn't clarify what 'stocking' entails (e.g., saving, bookmarking, or adding to a list), whether it's idempotent, requires authentication, or has side effects. This leaves critical behavioral traits unspecified for a mutation tool.

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 in Japanese that directly states the tool's action. It's front-loaded with the core purpose, though it could be slightly more informative without sacrificing brevity, earning a high score for 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 tool is a mutation (implied by 'stocks') with no annotations and no output schema, the description is incomplete. It lacks details on behavior, return values, error conditions, or how it fits with siblings like 'unstock_item', making it inadequate for safe and effective use by an agent.

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 '記事ID' (article ID). The description doesn't add any meaning beyond this, such as format examples or sourcing details, but the schema provides adequate information, meeting the baseline for high coverage.

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 '指定された記事をストックします' (Stocks the specified article) provides a basic verb+resource combination, stating the action (stock) and target (article). However, it doesn't differentiate from sibling tools like 'unstock_item' or explain what 'stocking' means in this context beyond the literal translation, making it somewhat vague.

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 (e.g., authentication), when not to use it (e.g., if already stocked), or refer to related tools like 'unstock_item' or 'is_item_stocked' for checking status, leaving the agent without context for decision-making.

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