Skip to main content
Glama
GeorgeNance

Hacker News MCP Server

by GeorgeNance

get_top_hackernews_stories

Retrieve trending stories from Hacker News by specifying the number of top articles to fetch, enabling access to current community discussions and technology news.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo

Implementation Reference

  • The handler function for the 'get_top_stories' tool, which retrieves top Hacker News stories by fetching top story IDs and details for a configurable number of stories.
    private async getTopStories(args: { count?: number; include_text?: boolean }) {
      const count = Math.min(args?.count || 30, 100);
      const includeText = args?.include_text || false;
    
      try {
        // Get top story IDs
        const response = await this.axiosInstance.get<number[]>('/topstories.json');
        const storyIds = response.data.slice(0, count);
    
        // Fetch story details
        const stories = await Promise.all(
          storyIds.map(async (id) => {
            const story = await fetchItem(this.axiosInstance, id);
            if (story && story.type === 'story') {
              return {
                id: story.id,
                title: story.title,
                url: story.url,
                by: story.by,
                score: story.score,
                time:
                  typeof story.time === 'number'
                    ? new Date(story.time * 1000).toISOString()
                    : story.time
                      ? new Date(Date.parse(story.time)).toISOString()
                      : undefined,
                descendants: story.descendants,
                ...(includeText && story.text ? { text: story.text } : {}),
              };
            }
            return null;
          }),
        );
    
        const validStories = stories.filter(Boolean);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(validStories, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to fetch top stories: ${error instanceof Error ? error.message : 'Unknown error'}`,
        );
      }
    }
  • The input schema definition for the 'get_top_stories' tool, specifying parameters for count and include_text.
      name: 'get_top_stories',
      description: 'Get the latest top stories from Hacker News',
      inputSchema: {
        type: 'object',
        properties: {
          count: {
            type: 'number',
            description: 'Number of stories to fetch (1-100)',
            minimum: 1,
            maximum: 100,
            default: 30,
          },
          include_text: {
            type: 'boolean',
            description: 'Whether to include story text content',
            default: false,
          },
        },
      },
    },
  • src/index.ts:176-177 (registration)
    Registration of the tool handler in the switch statement for CallToolRequestSchema.
    case 'get_top_stories':
      return await this.getTopStories(request.params.arguments ?? {});
  • Helper function `fetchItem` used by the handler to fetch individual story details from the Hacker News API.
    export async function fetchItem(axiosInstance: AxiosInstance, id: number): Promise<Story | null> {
      try {
        const response = await axiosInstance.get<Story>(`/item/${id}.json`);
        return response.data;
      } catch (error) {
        console.error(`Error fetching item ${id}:`, error);
        return null;
      }
    }
  • Helper function to create the Axios instance configured for the Hacker News API base URL.
    export function createAxiosInstance(): AxiosInstance {
      return axios.create({
        baseURL: 'https://hacker-news.firebaseio.com/v0',
        timeout: 10000,
      });
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/GeorgeNance/hackernews-mcp'

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