Skip to main content
Glama
Selenium39

Qiita API MCP Server

get_item

Retrieve detailed information about specific articles from the Qiita developer community platform using article IDs.

Instructions

指定された記事の詳細情報を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes記事ID

Implementation Reference

  • Handler definition for the 'get_item' tool. Parses input using itemIdSchema and executes by calling client.getItem(itemId).
    get_item: {
      schema: itemIdSchema,
      execute: async ({ itemId }, client) => client.getItem(itemId),
    },
  • MCP tool schema definition for 'get_item', specifying input schema with required 'itemId' string.
    {
      name: 'get_item',
      description: '指定された記事の詳細情報を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          itemId: {
            type: 'string',
            description: '記事ID',
          },
        },
        required: ['itemId'],
      },
    },
  • QiitaApiClient method that performs the actual HTTP GET request to retrieve the item details from Qiita API.
    async getItem(itemId: string) {
      const response = await this.client.get(`/items/${itemId}`);
      return response.data;
    }
  • Zod schema used for input validation in the get_item 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 full burden. It states it 'retrieves' information, implying a read-only operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or what happens if the itemId is invalid. For a tool with zero annotation coverage, 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, efficient sentence in Japanese that directly states the tool's purpose. It's appropriately sized and front-loaded with no wasted words, 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 tool's simplicity (1 parameter, no output schema, no annotations), the description is minimal but incomplete. It doesn't cover what 'detailed information' includes, authentication needs, or error handling. For a read operation in a context with many sibling tools, more context would help the agent use it correctly.

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 input schema has 100% description coverage, with itemId documented as '記事ID' (article ID). The description adds no additional meaning beyond this, as it doesn't explain format, constraints, or examples. With high schema coverage, the baseline is 3, and the description doesn't compensate or add value.

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 '指定された記事の詳細情報を取得します' (Retrieves detailed information of the specified article) clearly states the action (retrieves) and resource (article details), but it's vague about what 'detailed information' includes. It distinguishes from siblings like get_items (plural) and get_item_comments, but doesn't specify how it differs from other get_* tools that might also retrieve article-related data.

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. The description doesn't mention prerequisites (e.g., authentication), when not to use it, or compare it to siblings like get_items (for listing) or get_item_comments (for comments only). The agent must infer usage from the tool name alone.

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