Skip to main content
Glama
Selenium39

Qiita API MCP Server

get_user_followees

Retrieve a user's following list on Qiita to analyze connections and discover content creators within the developer community.

Instructions

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

Input Schema

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

Implementation Reference

  • Defines the handler for the 'get_user_followees' tool, including Zod input schema and async execute function that calls the Qiita API client.
    get_user_followees: {
      schema: userIdSchema.merge(paginationSchema),
      execute: async ({ userId, page, perPage }, client) =>
        client.getUserFollowees(userId, page, perPage),
    },
  • MCP protocol tool schema definition for 'get_user_followees', used for listing tools.
    {
      name: 'get_user_followees',
      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'],
      },
    },
  • The supporting method in QiitaApiClient that performs the actual HTTP request to fetch the list of users that the specified user is following.
    async getUserFollowees(userId: string, page = 1, perPage = 20) {
      const response = await this.client.get(`/users/${userId}/followees`, {
        params: { page, per_page: perPage },
      });
      return response.data;
    }
  • src/index.ts:26-28 (registration)
    Registers the request handler for listing tools, which returns the tools array including 'get_user_followees'.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/index.ts:30-65 (registration)
    Registers the request handler for calling tools, which uses toolHandlers[name] to execute 'get_user_followees'.
    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,
        };
      }
    });
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 a list but doesn't mention pagination behavior (implied by parameters), rate limits, authentication needs, or what happens with invalid inputs. For a read operation with no annotation coverage, this leaves significant gaps in understanding how the tool behaves beyond basic functionality.

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 front-loaded with the core action and resource, making it easy to parse. 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 the complexity (a read operation with pagination), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, return format, or pagination details, which are critical for an agent to use the tool effectively. The high schema coverage helps but doesn't compensate for missing context on outputs and behavior.

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 semantics beyond what the input schema provides. Schema description coverage is 100%, with clear documentation for userId, page, and perPage parameters. The description doesn't explain how these parameters interact (e.g., pagination for large follow lists) or provide additional context, so it meets the baseline for high schema coverage.

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 follow list of the specified user). It uses a specific verb ('取得します' - get/retrieve) and resource ('フォロー一覧' - follow list), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'get_user_followers' (which gets followers rather than followees), so it doesn't reach the highest 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_user_followers' (for followers) or 'get_user' (for user details), nor does it specify prerequisites or contexts. The agent must infer usage from the tool name and description 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