Skip to main content
Glama
Selenium39

Qiita API MCP Server

get_user

Retrieve detailed information about a specific user on the Qiita developer community platform by providing their user ID.

Instructions

指定されたユーザーの詳細情報を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesユーザーID

Implementation Reference

  • Handler definition for the 'get_user' MCP tool. Validates input using userIdSchema and executes by calling QiitaApiClient.getUser(userId). This is the core execution logic invoked when the tool is called.
    get_user: {
      schema: userIdSchema,
      execute: async ({ userId }, client) => client.getUser(userId),
    },
  • Tool schema definition for 'get_user', including name, description, and JSON input schema. Used for MCP listTools response and tool discovery.
    {
      name: 'get_user',
      description: '指定されたユーザーの詳細情報を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          userId: {
            type: 'string',
            description: 'ユーザーID',
          },
        },
        required: ['userId'],
      },
    },
  • Supporting method in QiitaApiClient that performs the actual API request to fetch user details from Qiita API. Called by the tool handler.
    async getUser(userId: string) {
      const response = await this.client.get(`/users/${userId}`);
      return response.data;
    }
  • Zod schema for userId input validation, used by multiple tools including 'get_user' for runtime parsing in the handler.
    const userIdSchema = z.object({
      userId: z.string(),
    });
  • src/index.ts:26-28 (registration)
    Registration of listTools handler that returns the tools array containing 'get_user' definition for MCP protocol.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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 only states what the tool does (retrieves user details) without mentioning whether it's a read-only operation, what permissions are required, how errors are handled, or the format of the returned data. For a tool with zero annotation coverage, this is a significant gap in transparency.

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, making it easy for an agent to parse quickly. Every part of the sentence earns its place by conveying essential information.

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 of a user retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't explain what '詳細情報' (detailed information) includes, how the data is structured, or potential error conditions. This leaves the agent with insufficient context to understand the tool's full behavior and output.

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' documented in the schema as 'ユーザーID'. The description doesn't add any meaning beyond this, such as explaining what constitutes a valid user ID or where to find it. With high schema coverage, the baseline score of 3 is appropriate, as the schema already provides adequate parameter documentation.

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: '指定されたユーザーの詳細情報を取得します' (Retrieves detailed information for a specified user). It uses a specific verb (取得/retrieve) and resource (ユーザーの詳細情報/user details). However, it doesn't explicitly differentiate from sibling tools like 'get_authenticated_user' or 'get_users', which is why it doesn't reach 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' over 'get_authenticated_user' (for current user) or 'get_users' (for multiple users), nor does it specify prerequisites or exclusions. This leaves the agent without context for tool selection.

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