Skip to main content
Glama
Selenium39

Qiita API MCP Server

get_tag_items

Retrieve articles associated with a specific tag from Qiita, the Japanese developer community platform, using tag ID and pagination parameters.

Instructions

指定されたタグの記事一覧を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagIdYesタグID
pageNoページ番号(1-100)
perPageNo1ページあたりの件数(1-100)

Implementation Reference

  • Handler definition for the 'get_tag_items' tool. It defines the input schema by merging tagIdSchema and paginationSchema, and the execute function which calls client.getTagItems with the parsed arguments.
    get_tag_items: {
      schema: tagIdSchema.merge(paginationSchema),
      execute: async ({ tagId, page, perPage }, client) =>
        client.getTagItems(tagId, page, perPage),
    },
  • MCP tool schema definition for 'get_tag_items', including name, description, and inputSchema for tool listing.
    {
      name: 'get_tag_items',
      description: '指定されたタグの記事一覧を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          tagId: {
            type: 'string',
            description: 'タグID',
          },
          page: {
            type: 'number',
            description: 'ページ番号(1-100)',
            default: 1,
          },
          perPage: {
            type: 'number',
            description: '1ページあたりの件数(1-100)',
            default: 20,
          },
        },
        required: ['tagId'],
      },
    },
  • Supporting method in QiitaApiClient that performs the actual API call to retrieve items associated with a specific tag from the Qiita API.
    async getTagItems(tagId: string, page = 1, perPage = 20) {
      const response = await this.client.get(`/tags/${tagId}/items`, {
        params: { page, per_page: perPage },
      });
      return response.data;
    }
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 of behavioral disclosure. It mentions getting a list of articles but doesn't describe the return format, pagination behavior, error handling, or any rate limits. This is a significant gap for a tool with no annotation coverage.

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 purpose. It's front-loaded with no wasted words, though it could be slightly more structured for clarity.

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 complexity (a read operation with pagination), no annotations, and no output schema, the description is incomplete. It doesn't explain what the returned list contains, how results are formatted, or any behavioral traits, making it inadequate for full agent understanding.

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 clear documentation for 'tagId', 'page', and 'perPage'. The description doesn't add any meaning beyond this, such as explaining what a 'tagId' represents or how pagination works. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states '指定されたタグの記事一覧を取得します' (Get a list of articles for a specified tag), which clearly indicates the verb (get) and resource (articles for a tag). However, it doesn't distinguish this from sibling tools like 'get_items' (which likely gets all items) or 'get_user_items' (which gets items by user), leaving the purpose somewhat vague in 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_items' or 'get_user_items', nor does it specify prerequisites or exclusions, leaving the agent with no contextual usage information.

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