Skip to main content
Glama
devabdultech

Hacker News MCP Server

getStories

Retrieve Hacker News stories by category (top, new, best, ask, show, job) to access trending discussions and content from the community.

Instructions

Get multiple stories by type (top, new, best, ask, show, job)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesThe type of stories to fetch
limitNoThe maximum number of stories to fetch

Implementation Reference

  • src/index.ts:91-111 (registration)
    Registration of the 'getStories' tool in the ListToolsRequestSchema handler, including name, description, and input schema definition.
    {
      name: "getStories",
      description:
        "Get multiple stories by type (top, new, best, ask, show, job)",
      inputSchema: {
        type: "object",
        properties: {
          type: {
            type: "string",
            enum: ["top", "new", "best", "ask", "show", "job"],
            description: "The type of stories to fetch",
          },
          limit: {
            type: "number",
            description: "The maximum number of stories to fetch",
            default: 30,
          },
        },
        required: ["type"],
      },
    },
  • The primary handler for the 'getStories' tool in the CallToolRequestSchema switch statement. Fetches story IDs by type from HN API, retrieves items, formats stories, and constructs a response with a numbered list.
    case "getStories": {
      const { type, limit = 30 } = args as {
        type: "top" | "new" | "best" | "ask" | "show" | "job";
        limit?: number;
      };
      try {
        let storyIds: number[] = [];
    
        switch (type) {
          case "top":
            storyIds = await hnApi.getTopStories(limit);
            break;
          case "new":
            storyIds = await hnApi.getNewStories(limit);
            break;
          case "best":
            storyIds = await hnApi.getBestStories(limit);
            break;
          case "ask":
            storyIds = await hnApi.getAskStories(limit);
            break;
          case "show":
            storyIds = await hnApi.getShowStories(limit);
            break;
          case "job":
            storyIds = await hnApi.getJobStories(limit);
            break;
        }
    
        const items = await hnApi.getItems(storyIds);
        const stories = items
          .filter((item) => item && item.type === "story")
          .map(formatStory);
    
        if (stories.length === 0) {
          return {
            content: [{ type: "text", text: "No stories found." }],
          };
        }
    
        const text = stories
          .map(
            (story, index) =>
              `${index + 1}. ${story.title}\n` +
              `   ID: ${story.id}\n` +
              `   URL: ${story.url || "(text post)"}\n` +
              `   Points: ${story.score} | Author: ${story.by} | Comments: ${story.descendants}\n\n`
          )
          .join("");
    
        return {
          content: [{ type: "text", text: text.trim() }],
        };
      } catch (err) {
        const error = err as Error;
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to fetch stories: ${error.message}`
        );
      }
    }
  • Helper function used by the handler to format raw Hacker News story items into a standardized Story object.
    export function formatStory(item: any): Story {
      return {
        id: item.id,
        title: item.title,
        url: item.url,
        text: item.text,
        by: item.by,
        score: item.score || 0,
        time: item.time,
        descendants: item.descendants || 0,
        kids: item.kids || [],
        type: "story",
      };
    }
  • Helper methods in HackerNewsAPI class to fetch story ID lists for different categories (top, new, best, ask, show, job), used by the getStories handler.
    async getTopStories(limit: number = 30): Promise<number[]> {
      const response = await fetch(`${API_BASE_URL}/topstories.json`);
      const ids = (await response.json()) as number[];
      return ids.slice(0, limit);
    }
    
    /**
     * Fetch new stories
     */
    async getNewStories(limit: number = 30): Promise<number[]> {
      const response = await fetch(`${API_BASE_URL}/newstories.json`);
      const ids = (await response.json()) as number[];
      return ids.slice(0, limit);
    }
    
    /**
     * Fetch best stories
     */
    async getBestStories(limit: number = 30): Promise<number[]> {
      const response = await fetch(`${API_BASE_URL}/beststories.json`);
      const ids = (await response.json()) as number[];
      return ids.slice(0, limit);
    }
    
    /**
     * Fetch ask stories
     */
    async getAskStories(limit: number = 30): Promise<number[]> {
      const response = await fetch(`${API_BASE_URL}/askstories.json`);
      const ids = (await response.json()) as number[];
      return ids.slice(0, limit);
    }
    
    /**
     * Fetch show stories
     */
    async getShowStories(limit: number = 30): Promise<number[]> {
      const response = await fetch(`${API_BASE_URL}/showstories.json`);
      const ids = (await response.json()) as number[];
      return ids.slice(0, limit);
    }
    
    /**
     * Fetch job stories
     */
    async getJobStories(limit: number = 30): Promise<number[]> {
      const response = await fetch(`${API_BASE_URL}/jobstories.json`);
      const ids = (await response.json()) as number[];
      return ids.slice(0, limit);
    }
  • Helper method to batch fetch multiple HN items by IDs, used in the getStories handler.
    async getItems(ids: number[]): Promise<any[]> {
      return Promise.all(ids.map((id) => this.getItem(id)));
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't mention pagination behavior, rate limits, authentication requirements, or what format/structure the returned stories have. For a tool fetching multiple items, this leaves significant behavioral gaps.

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 with zero wasted words. It's appropriately sized for this tool's complexity and front-loads the essential information about what the tool does.

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 for a tool that fetches multiple items. It doesn't explain what 'stories' are in this context, what fields they contain, how results are ordered/paginated, or any error conditions. The description alone leaves too many contextual gaps.

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 description coverage is 100%, so the schema already documents both parameters thoroughly. The description mentions 'by type' which aligns with the 'type' parameter but adds no additional semantic context beyond what the schema provides. The baseline of 3 is appropriate when 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 verb ('Get') and resource ('multiple stories'), specifying the action and target. It distinguishes the tool by mentioning story types, but doesn't explicitly differentiate from siblings like 'getStory' or 'getStoryWithComments' beyond the plural 'multiple' aspect.

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 like 'getStory', 'getStoryWithComments', or 'search'. It mentions story types but doesn't explain why one would choose this tool over others for fetching stories, leaving usage context implicit at best.

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