Skip to main content
Glama
Selenium39

Qiita API MCP Server

follow_user

Follow a specific user on Qiita to track their articles and activities within the Japanese developer community platform.

Instructions

指定されたユーザーをフォローします

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesユーザーID

Implementation Reference

  • The handler definition for the 'follow_user' tool, which validates input using userIdSchema and executes by calling client.followUser(userId).
    follow_user: {
      schema: userIdSchema,
      execute: async ({ userId }, client) => client.followUser(userId),
    },
  • The MCP tool schema definition for 'follow_user', including input schema for userId.
    {
      name: 'follow_user',
      description: '指定されたユーザーをフォローします',
      inputSchema: {
        type: 'object',
        properties: {
          userId: {
            type: 'string',
            description: 'ユーザーID',
          },
        },
        required: ['userId'],
      },
    },
  • The Qiita API client method that performs the actual HTTP PUT request to follow a user.
    async followUser(userId: string) {
      this.assertAuthenticated();
      await this.client.put(`/users/${userId}/following`);
      return { success: true };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action but doesn't mention authentication requirements, rate limits, whether following is reciprocal, what happens if the user doesn't exist, or what the response looks like. For a mutation tool with zero annotation coverage, this is insufficient.

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 for a simple tool with one parameter.

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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after following (e.g., success/failure response, error conditions), doesn't mention authentication requirements, and provides no context about the social following system's rules or limitations.

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 schema description coverage is 100%, with the single parameter 'userId' clearly documented in the schema. The description doesn't add any meaningful parameter information beyond what's already in the structured schema, 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 action ('follow') and target ('specified user'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'unfollow_user' or explain how it differs from 'is_user_followed', missing full sibling differentiation.

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 like 'unfollow_user', 'is_user_followed', or 'get_user_followees/followers'. There's no mention of prerequisites, constraints, or appropriate contexts for following a user.

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