Skip to main content
Glama
wei
by wei

Get Comments for a Story

get-story-comments

Retrieve all comments for a specific HackerNews story using its ID, with pagination support for browsing through discussion threads.

Instructions

Get all comments for a specific story by story ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsPerPageNoNumber of results per page (default: 20)
pageNoPage number for pagination (default: 0)
storyIdYesThe ID of the story

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsYes
pageYes
nbHitsYes
nbPagesYes
hitsPerPageYes

Implementation Reference

  • Executes the tool by querying HackerNews API for comments on a specific story ID using tags 'comment,story_${storyId}', with optional pagination, and returns formatted results.
    async ({ storyId, page, hitsPerPage }) => {
      const params = new URLSearchParams();
      params.append('tags', `comment,story_${storyId}`);
      if (page !== undefined) params.append('page', page.toString());
      if (hitsPerPage !== undefined) params.append('hitsPerPage', hitsPerPage.toString());
      
      const endpoint = `/search?${params.toString()}`;
      const result = await fetchHN(endpoint);
      
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
        structuredContent: result
      };
    }
  • Input schema requires storyId (number) and optional page/hitsPerPage; output schema defines search result structure.
    {
      title: 'Get Comments for a Story',
      description: 'Get all comments for a specific story by story ID',
      inputSchema: {
        storyId: z.number().describe('The ID of the story'),
        page: z.number().optional().describe('Page number for pagination (default: 0)'),
        hitsPerPage: z.number().optional().describe('Number of results per page (default: 20)')
      },
      outputSchema: {
        hits: z.array(z.any()),
        nbHits: z.number(),
        nbPages: z.number(),
        page: z.number(),
        hitsPerPage: z.number()
      }
  • src/index.ts:371-402 (registration)
    Registers the 'get-story-comments' tool with McpServer, including schema and handler function.
      'get-story-comments',
      {
        title: 'Get Comments for a Story',
        description: 'Get all comments for a specific story by story ID',
        inputSchema: {
          storyId: z.number().describe('The ID of the story'),
          page: z.number().optional().describe('Page number for pagination (default: 0)'),
          hitsPerPage: z.number().optional().describe('Number of results per page (default: 20)')
        },
        outputSchema: {
          hits: z.array(z.any()),
          nbHits: z.number(),
          nbPages: z.number(),
          page: z.number(),
          hitsPerPage: z.number()
        }
      },
      async ({ storyId, page, hitsPerPage }) => {
        const params = new URLSearchParams();
        params.append('tags', `comment,story_${storyId}`);
        if (page !== undefined) params.append('page', page.toString());
        if (hitsPerPage !== undefined) params.append('hitsPerPage', hitsPerPage.toString());
        
        const endpoint = `/search?${params.toString()}`;
        const result = await fetchHN(endpoint);
        
        return {
          content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
          structuredContent: result
        };
      }
    );
  • Shared helper utility to make API calls to HackerNews Algolia API, used by get-story-comments and other tools.
    async function fetchHN(endpoint: string): Promise<any> {
      const response = await fetch(`${HN_API_BASE}${endpoint}`);
      if (!response.ok) {
        throw new Error(`HN API error: ${response.status} ${response.statusText}`);
      }
      return await response.json();
    }
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 it 'gets all comments' but doesn't clarify if this is a read-only operation, how pagination works beyond the schema, or any rate limits or authentication needs. This is inadequate for a tool with parameters and no annotation coverage.

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 that front-loads the core purpose without any wasted words. It's appropriately sized for a straightforward retrieval tool, earning the highest score for conciseness.

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 tool's moderate complexity (3 parameters, 1 required), 100% schema coverage, and the presence of an output schema (which handles return values), the description is mostly complete. However, it lacks behavioral context and usage guidelines, which are minor gaps in an otherwise well-supported setup.

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%, so the schema already documents all parameters (storyId, hitsPerPage, page) with their types and defaults. The description adds no additional meaning beyond implying retrieval by story ID, which is already covered in the schema, resulting in a baseline score.

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 verb ('Get') and resource ('all comments for a specific story'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get-item' or 'get-latest-comments', which might also retrieve comments in different contexts, so it doesn't reach the highest score.

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 siblings like 'get-latest-comments' for recent comments or 'get-item' for general item retrieval, leaving the agent without context for selection among similar tools.

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/wei/hn-mcp-server-vibe'

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