Skip to main content
Glama
Selenium39

Qiita API MCP Server

get_user_followers

Retrieve a list of followers for a specific Qiita user. Use this tool to access user follower data with pagination controls for efficient browsing.

Instructions

指定されたユーザーのフォロワー一覧を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesユーザーID
pageNoページ番号(1-100)
perPageNo1ページあたりの件数(1-100)

Implementation Reference

  • The handler definition for the 'get_user_followers' tool, including Zod schema for input validation and the execute function that delegates to the QiitaApiClient.
    get_user_followers: {
      schema: userIdSchema.merge(paginationSchema),
      execute: async ({ userId, page, perPage }, client) =>
        client.getUserFollowers(userId, page, perPage),
    },
  • The MCP tool schema definition for 'get_user_followers', including name, description, and input schema used for listing tools.
    {
      name: 'get_user_followers',
      description: '指定されたユーザーのフォロワー一覧を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          userId: {
            type: 'string',
            description: 'ユーザーID',
          },
          page: {
            type: 'number',
            description: 'ページ番号(1-100)',
            default: 1,
          },
          perPage: {
            type: 'number',
            description: '1ページあたりの件数(1-100)',
            default: 20,
          },
        },
        required: ['userId'],
      },
    },
  • src/index.ts:30-65 (registration)
    The MCP server registration for tool calls, where toolHandlers[name] is retrieved, input is parsed with the handler's schema, and the execute function is invoked with the Qiita client.
    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];
    
      try {
        if (!handler) {
          throw new Error(`未知のツール: ${name}`);
        }
    
        const parsedArgs = handler.schema.parse(args ?? {});
        const result = await handler.execute(parsedArgs, qiita);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error: any) {
        const message = error?.message ?? String(error);
        return {
          content: [
            {
              type: 'text',
              text: `エラーが発生しました: ${message}`,
            },
          ],
          isError: true,
        };
      }
    });
  • The helper method in QiitaApiClient that performs the actual HTTP request to fetch the user's followers from the Qiita API.
    async getUserFollowers(userId: string, page = 1, perPage = 20) {
      const response = await this.client.get(`/users/${userId}/followers`, {
        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 states the tool retrieves data (a read operation) but doesn't mention any behavioral traits like pagination behavior (implied by page/perPage parameters but not explained), rate limits, authentication requirements, or error conditions. For a tool with no annotation coverage, this is a significant gap.

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 unnecessary words. It's appropriately sized and front-loaded, with zero wasted content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It covers the basic purpose but lacks behavioral context, usage guidelines, and output details. Without annotations or an output schema, the agent must infer behavior from the description alone, which is insufficient for full 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 userId, page, and perPage parameters. The description doesn't add any semantic details beyond what the schema provides (e.g., it doesn't explain what 'followers' means in this context or how pagination works). With high schema coverage, the baseline score of 3 is appropriate.

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 tool's purpose: '指定されたユーザーのフォロワー一覧を取得します' (Get the list of followers for a specified user). It uses a specific verb (取得/retrieve) and resource (ユーザーのフォロワー/user's followers). However, it doesn't explicitly distinguish itself from sibling tools like get_user_followees or get_users, which would be needed for a score of 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose get_user_followers over get_user_followees (which likely retrieves users the target user follows) or get_users (which might retrieve general user lists). There's no context about prerequisites or exclusions.

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