Skip to main content
Glama
devabdultech

Hacker News MCP Server

by devabdultech

getUser

Retrieve Hacker News user profiles by ID to access karma, about sections, and submission history.

Instructions

Get a user profile by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the user

Implementation Reference

  • Main handler for the 'getUser' tool: validates input using UserRequestSchema, fetches user data via hnApi.getUser, formats it with formatUser, constructs response text with user profile details.
    case "getUser": {
      const validatedArgs = validateInput(UserRequestSchema, args);
      const { id } = validatedArgs;
    
      const user = await hnApi.getUser(id);
    
      if (!user) {
        throw new McpError(
          ErrorCode.InvalidParams,
          `User with ID ${id} not found`
        );
      }
    
      const formattedUser = formatUser(user);
      const text =
        `User Profile:\n` +
        `Username: ${formattedUser.id}\n` +
        `Karma: ${formattedUser.karma}\n` +
        `Created: ${new Date(formattedUser.created * 1000).toISOString()}\n` +
        (formattedUser.about ? `\nAbout:\n${formattedUser.about}\n` : "");
    
      return {
        content: [{ type: "text", text: text.trim() }],
      };
    }
  • src/index.ts:150-160 (registration)
    Registers the 'getUser' tool in the ListTools response, specifying name, description, and input schema.
    {
      name: "getUser",
      description: "Get a user profile by ID",
      inputSchema: {
        type: "object",
        properties: {
          id: { type: "string", description: "The ID of the user" },
        },
        required: ["id"],
      },
    },
  • Zod schema for validating the input parameters of the 'getUser' tool (user ID as string).
    export const UserRequestSchema = z.object({
      id: z.string(),
    });
  • HackerNewsAPI method that fetches user profile data from the official HN Firebase API endpoint.
    async getUser(id: string): Promise<any> {
      const response = await fetch(`${API_BASE_URL}/user/${id}.json`);
      return response.json();
    }
  • Helper function to format raw user data from HN API into a structured User interface.
    export function formatUser(user: any): User {
      return {
        id: user.id,
        created: user.created,
        karma: user.karma,
        about: user.about,
        submitted: user.submitted,
      };
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, and the description does not disclose behavioral details like error handling or rate limits. However, for a simple read operation, the minimal disclosure is acceptable.

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?

Single sentence, no wasted words. Front-loaded with the key action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity (one required parameter, no output schema), the description is mostly adequate. It could mention what a user profile contains, but not essential.

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 coverage is 100% and the parameter 'id' is described in the schema as 'The ID of the user'. The description merely echoes this, adding no additional meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'user profile', with the parameter 'by ID'. It distinguishes from sibling tools like getComment and getStory.

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 on when to use this tool versus alternatives such as getUserSubmissions or search. The description only states what it does, not the context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.