Skip to main content
Glama
devabdultech

Hacker News MCP Server

getCommentTree

Retrieve nested comment threads for Hacker News stories to analyze discussions and follow conversations.

Instructions

Get a comment tree for a story

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storyIdYesThe ID of the story

Implementation Reference

  • The handler for the 'getCommentTree' tool. Validates the input using CommentTreeRequestSchema, fetches the story with comments using algoliaApi.getStoryWithComments, recursively formats the comment tree into a textual representation with indentation, and returns it as text content.
    case "getCommentTree": {
      const validatedArgs = validateInput(CommentTreeRequestSchema, args);
      const { storyId } = validatedArgs;
      try {
        const data = await algoliaApi.getStoryWithComments(storyId);
    
        if (!data || !data.children || data.children.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: `No comments found for story ID: ${storyId}`,
              },
            ],
          };
        }
    
        const formatCommentTree = (comment: any, depth = 0): string => {
          const indent = "  ".repeat(depth);
          let text = `${indent}Comment by ${comment.author} (ID: ${comment.id}):\n`;
          text += `${indent}${comment.text}\n\n`;
    
          if (comment.children) {
            text += comment.children
              .map((child: any) => formatCommentTree(child, depth + 1))
              .join("");
          }
          return text;
        };
    
        const text =
          `Comment tree for Story ID: ${storyId}\n\n` +
          data.children
            .map((comment: any) => formatCommentTree(comment))
            .join("");
    
        return {
          content: [{ type: "text", text: text.trim() }],
        };
      } catch (err) {
        const error = err as Error;
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to fetch comment tree: ${error.message}`
        );
      }
    }
  • src/index.ts:139-149 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema for getCommentTree.
    {
      name: "getCommentTree",
      description: "Get a comment tree for a story",
      inputSchema: {
        type: "object",
        properties: {
          storyId: { type: "number", description: "The ID of the story" },
        },
        required: ["storyId"],
      },
    },
  • Zod schema used for input validation of the getCommentTree tool, requiring a positive integer storyId.
    export const CommentTreeRequestSchema = z.object({
      storyId: z.number().int().positive(),
    });
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 tool retrieves data ('Get'), implying a read-only operation, but doesn't specify permissions, rate limits, pagination, or what a 'comment tree' entails structurally. This leaves significant behavioral gaps for an agent.

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, clear sentence with no wasted words. It's front-loaded with the core purpose, making it highly efficient and easy to parse.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what a 'comment tree' returns (e.g., nested structure, fields included), which is critical for a tool with siblings that handle comments differently. This leaves the agent with insufficient context for effective use.

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 input schema has 100% description coverage, with 'storyId' documented as 'The ID of the story'. The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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 ('Get') and resource ('comment tree for a story'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'getComment' or 'getComments', which likely retrieve individual or multiple comments rather than a hierarchical tree structure.

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. With siblings like 'getComment', 'getComments', and 'getStoryWithComments', there's no indication of when this specific tree retrieval is appropriate, leaving usage context unclear.

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/devabdultech/hn-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server