Skip to main content
Glama
Selenium39

Qiita API MCP Server

follow_tag

Subscribe to specific tags on Qiita to receive updates and discover relevant developer content in your feed.

Instructions

指定されたタグをフォローします

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagIdYesタグID

Implementation Reference

  • The handler for the 'follow_tag' tool. It uses tagIdSchema for input validation and delegates execution to QiitaApiClient.followTag(tagId).
    follow_tag: {
      schema: tagIdSchema,
      execute: async ({ tagId }, client) => client.followTag(tagId),
    },
  • MCP tool definition for 'follow_tag' including the input JSON schema requiring a 'tagId' string.
    {
      name: 'follow_tag',
      description: '指定されたタグをフォローします',
      inputSchema: {
        type: 'object',
        properties: {
          tagId: {
            type: 'string',
            description: 'タグID',
          },
        },
        required: ['tagId'],
      },
    },
  • src/index.ts:26-28 (registration)
    Registration of the tool list request handler, which returns the tools array containing 'follow_tag'.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/index.ts:30-65 (registration)
    Registration of the call tool request handler, which dynamically dispatches to toolHandlers[name].execute for 'follow_tag'.
    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 QiitaApiClient method that performs the actual API call to follow the specified tag.
    async followTag(tagId: string) {
      this.assertAuthenticated();
      await this.client.put(`/tags/${tagId}/following`);
      return { success: 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 action (follow a tag) but doesn't describe what 'follow' entails (e.g., notifications, updates), whether it requires authentication, if it's idempotent, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral context.

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 ('指定されたタグをフォローします'), which directly states the action without waste. It's appropriately sized and front-loaded, with every word contributing to the core purpose.

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 complexity (a mutation with no annotations, 1 parameter, no output schema), the description is incomplete. It lacks details on behavior, authentication needs, return values, or error handling. For a follow action, more context (e.g., what 'follow' means, idempotency) 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?

Schema description coverage is 100%, with the single parameter 'tagId' documented in the schema as 'タグID' (tag ID). The description doesn't add any meaning beyond this (e.g., format, source, or examples). Baseline is 3 since the schema does the heavy lifting, but no extra value is provided.

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 '指定されたタグをフォローします' (Follows the specified tag) clearly states the verb (follow) and resource (tag), making the purpose understandable. It distinguishes from siblings like follow_user (follows users) and unfollow_tag (unfollows tags), though it doesn't explicitly mention this differentiation. The purpose is specific but lacks explicit sibling comparison.

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 prerequisites (e.g., authentication), when not to use it (e.g., if already following), or alternatives like is_tag_followed to check status first. Usage is implied by the action but lacks explicit context 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