Skip to main content
Glama
Selenium39

Qiita API MCP Server

get_item_stockers

Retrieve users who have bookmarked a specific Qiita article to analyze engagement and identify interested community members.

Instructions

指定された記事をストックしたユーザー一覧を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes記事ID
pageNoページ番号(1-100)
perPageNo1ページあたりの件数(1-100)

Implementation Reference

  • MCP tool handler for 'get_item_stockers'. Validates input using Zod schema (itemId + pagination) and executes by calling QiitaApiClient.getItemStockers.
    get_item_stockers: {
      schema: itemIdSchema.merge(paginationSchema),
      execute: async ({ itemId, page, perPage }, client) =>
        client.getItemStockers(itemId, page, perPage),
    },
  • MCP tool definition including name, description, and JSON input schema for 'get_item_stockers' used in listTools response.
    {
      name: 'get_item_stockers',
      description: '指定された記事をストックしたユーザー一覧を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          itemId: {
            type: 'string',
            description: '記事ID',
          },
          page: {
            type: 'number',
            description: 'ページ番号(1-100)',
            default: 1,
          },
          perPage: {
            type: 'number',
            description: '1ページあたりの件数(1-100)',
            default: 20,
          },
        },
        required: ['itemId'],
      },
    },
  • Core implementation in QiitaApiClient that performs the HTTP GET request to Qiita API endpoint /items/{itemId}/stockers to fetch stockers list.
    async getItemStockers(itemId: string, page = 1, perPage = 20) {
      const response = await this.client.get(`/items/${itemId}/stockers`, {
        params: { page, per_page: perPage },
      });
      return response.data;
    }
  • Shared Zod schema for pagination parameters used in get_item_stockers handler.
    const paginationSchema = z.object({
      page: z.number().int().min(1).max(100).default(1),
      perPage: z.number().int().min(1).max(100).default(20),
    });
  • Shared Zod schema for itemId parameter used in get_item_stockers handler.
    const itemIdSchema = z.object({
      itemId: z.string(),
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it retrieves a list, implying a read operation, but doesn't disclose behavioral traits like pagination behavior (implied by parameters but not described), rate limits, authentication needs, or what happens with invalid item IDs. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 purpose. It's front-loaded with the core functionality and has no unnecessary words or fluff. Every part of the sentence contributes to understanding what the tool does.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., list format, user details included), error conditions, or pagination details. For a tool with 3 parameters and no structured output information, the description should provide more context to be fully helpful.

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 the schema fully documents all parameters (itemId, page, perPage). The description doesn't add any meaning beyond what the schema provides—it mentions '指定された記事' (specified article) which corresponds to itemId but doesn't explain parameter interactions or usage. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('取得します' - get/retrieve) and resource ('指定された記事をストックしたユーザー一覧' - list of users who stocked the specified article). It distinguishes from siblings like 'get_item' (gets article details) or 'get_user_stocks' (gets articles stocked by a user). However, it doesn't explicitly contrast with 'is_item_stocked' (checks if article is stocked), which would make it a 5.

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 on when to use this tool versus alternatives. It doesn't mention when to use 'get_item_stockers' versus 'get_user_stocks' (which gets articles stocked by a user) or 'is_item_stocked' (which checks if an article is stocked). The description only states what it does, not when it's appropriate.

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