Skip to main content
Glama
Selenium39

Qiita API MCP Server

get_item_comments

Retrieve comments for a specific Qiita article to analyze discussions and user feedback. Provide the article ID to access all associated comments.

Instructions

指定された記事のコメント一覧を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes記事ID

Implementation Reference

  • Handler for the 'get_item_comments' tool. Parses arguments using itemIdSchema and delegates execution to the QiitaApiClient's getItemComments method.
    get_item_comments: {
      schema: itemIdSchema,
      execute: async ({ itemId }, client) => client.getItemComments(itemId),
    },
  • MCP tool definition including name, description, and JSON schema for input validation of 'get_item_comments'.
      name: 'get_item_comments',
      description: '指定された記事のコメント一覧を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          itemId: {
            type: 'string',
            description: '記事ID',
          },
        },
        required: ['itemId'],
      },
    },
  • Core implementation that performs the API request to retrieve comments for the specified item ID.
    async getItemComments(itemId: string) {
      const response = await this.client.get(`/items/${itemId}/comments`);
      return response.data;
    }
  • src/index.ts:11-35 (registration)
    Imports toolHandlers and selects the handler by name during tool call request handling, effectively registering the 'get_item_comments' handler.
    import { toolHandlers } from './tools/handlers.js';
    import { tools } from './tools/definitions.js';
    
    const server = new Server(
      {
        name: 'mcp-server-qiita',
        version: '1.0.0',
      },
      {
        capabilities: {
          tools: {},
        },
      }
    );
    
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
    
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      const accessToken = process.env.QIITA_ACCESS_TOKEN;
      const qiita = new QiitaApiClient(accessToken);
      const handler = toolHandlers[name];
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits such as whether this is a read-only operation (implied but not explicit), potential rate limits, authentication requirements, pagination behavior, or error conditions for invalid item IDs.

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 sentence in Japanese that directly states the tool's purpose without any fluff or redundant information. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 incomplete for a tool that likely returns a list of comments. It doesn't explain what the return value includes (e.g., comment text, authors, timestamps) or handle edge cases, leaving significant gaps in understanding how to use the tool effectively.

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 adds no parameter-specific information beyond what the schema provides (100% coverage with 'itemId' clearly documented as '記事ID'). Since the schema fully describes the single parameter, the baseline score of 3 is appropriate—the description doesn't compensate but doesn't need to given the comprehensive 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 verb ('取得します' - retrieve/get) and resource ('指定された記事のコメント一覧' - comments of a specified article), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_comment' (singular) or 'get_items' (articles vs comments), which prevents a perfect score.

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. For example, it doesn't mention whether to use 'get_comment' for a single comment or this tool for all comments of an article, nor does it specify prerequisites like needing the article ID from 'get_item' first.

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