Skip to main content
Glama
Selenium39

Qiita API MCP Server

unfollow_tag

Stop following a specific tag on Qiita to manage your feed content and focus on relevant topics in the developer community.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagIdYesタグID

Implementation Reference

  • The handler definition for the 'unfollow_tag' tool. It specifies the input schema (tagIdSchema) and the execute function that calls the QiitaApiClient's unfollowTag method.
    unfollow_tag: {
      schema: tagIdSchema,
      execute: async ({ tagId }, client) => client.unfollowTag(tagId),
    },
  • The JSON schema definition for the 'unfollow_tag' tool, used in the ListTools MCP response.
    {
      name: 'unfollow_tag',
      description: '指定されたタグのフォローを解除します',
      inputSchema: {
        type: 'object',
        properties: {
          tagId: {
            type: 'string',
            description: 'タグID',
          },
        },
        required: ['tagId'],
      },
    },
  • Zod schema for tagId input validation, referenced by the unfollow_tag handler and others.
    const tagIdSchema = z.object({
      tagId: z.string(),
    });
  • The Qiita API client method that implements the unfollow tag logic by sending a DELETE request to /tags/{tagId}/following.
    async unfollowTag(tagId: string) {
      this.assertAuthenticated();
      await this.client.delete(`/tags/${tagId}/following`);
      return { success: true };
    }
  • src/index.ts:30-52 (registration)
    The CallTool request handler in the MCP server that dispatches to toolHandlers[name].execute, effectively registering all tools in toolHandlers including unfollow_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),
            },
          ],
        };
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('unfollow') but doesn't clarify whether this is a destructive operation, requires authentication, has side effects (e.g., notifications), or what happens on success/failure. This leaves critical behavioral traits unspecified for a mutation tool.

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 conveys the core action without unnecessary words. It's front-loaded with the key information, making it highly concise and well-structured for quick comprehension.

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 insufficient. It doesn't explain the outcome (e.g., what 'unfollowed' means, return values, or error conditions), leaving gaps in understanding the tool's full behavior and integration context.

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 'tagId' clearly documented in the schema. The description doesn't add any semantic details beyond what the schema provides (e.g., format examples or sourcing guidance), so it meets the baseline for high schema coverage without extra value.

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 ('unfollow') and the resource ('tag'), making the purpose immediately understandable. However, it doesn't differentiate from its sibling 'unfollow_user' beyond the resource type, nor does it specify what 'unfollowing' entails in this context (e.g., removing from a personal list vs. public subscription).

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?

No guidance is provided on when to use this tool versus alternatives like 'unfollow_user' or 'is_tag_followed'. It lacks context such as prerequisites (e.g., must be following the tag first) or typical scenarios for unfollowing tags, leaving the agent to infer usage from the name 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