Skip to main content
Glama
wei
by wei

Get Posts by Author

get-posts-by-author

Retrieve all posts, stories, and comments from a specific HackerNews author. Filter results by content type and manage pagination to browse user contributions efficiently.

Instructions

Get all posts (stories, comments, etc.) by a specific author

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsPerPageNoNumber of results per page (default: 20)
pageNoPage number for pagination (default: 0)
tagsNoFilter by type (e.g., "story", "comment")
usernameYesThe username of the author

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsYes
pageYes
nbHitsYes
nbPagesYes
hitsPerPageYes

Implementation Reference

  • Handler function that constructs a HackerNews API search query using the 'author_USERNAME' tag combined with optional tags filter, paginates if specified, fetches from /search_by_date endpoint using shared fetchHN helper, and returns structured results.
    async ({ username, tags, page, hitsPerPage }) => {
      const params = new URLSearchParams();
      const authorTag = `author_${username}`;
      const combinedTags = tags ? `${authorTag},${tags}` : authorTag;
      params.append('tags', combinedTags);
      if (page !== undefined) params.append('page', page.toString());
      if (hitsPerPage !== undefined) params.append('hitsPerPage', hitsPerPage.toString());
      
      const endpoint = `/search_by_date?${params.toString()}`;
      const result = await fetchHN(endpoint);
      
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
        structuredContent: result
      };
    }
  • Input schema requires username, optional tags filter, page, hitsPerPage. Output schema defines search result structure with hits array, pagination info.
    {
      title: 'Get Posts by Author',
      description: 'Get all posts (stories, comments, etc.) by a specific author',
      inputSchema: {
        username: z.string().describe('The username of the author'),
        tags: z.string().optional().describe('Filter by type (e.g., "story", "comment")'),
        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:331-367 (registration)
    Full registration of the 'get-posts-by-author' tool on the MCP server, including name, metadata, schemas, and handler reference.
    // Tool 10: Get posts by author
    server.registerTool(
      'get-posts-by-author',
      {
        title: 'Get Posts by Author',
        description: 'Get all posts (stories, comments, etc.) by a specific author',
        inputSchema: {
          username: z.string().describe('The username of the author'),
          tags: z.string().optional().describe('Filter by type (e.g., "story", "comment")'),
          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 ({ username, tags, page, hitsPerPage }) => {
        const params = new URLSearchParams();
        const authorTag = `author_${username}`;
        const combinedTags = tags ? `${authorTag},${tags}` : authorTag;
        params.append('tags', combinedTags);
        if (page !== undefined) params.append('page', page.toString());
        if (hitsPerPage !== undefined) params.append('hitsPerPage', hitsPerPage.toString());
        
        const endpoint = `/search_by_date?${params.toString()}`;
        const result = await fetchHN(endpoint);
        
        return {
          content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
          structuredContent: result
        };
      }
    );
  • Shared utility function to make HTTP requests to the HackerNews Algolia API, handles errors and JSON parsing, used by the get-posts-by-author handler.
    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 the tool retrieves posts but doesn't cover critical aspects like whether it's read-only (implied by 'Get'), pagination behavior (hinted in schema but not explained), rate limits, authentication needs, or error handling. This leaves significant gaps for a tool with 4 parameters and potential API constraints.

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 ('Get all posts by a specific author') with a brief clarification in parentheses. There is no wasted verbiage, repetition, or structural issues, making it easy for an agent to parse quickly.

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

Completeness3/5

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

Given the tool has an output schema (which handles return values) and 100% schema coverage for parameters, the description's minimalism is partially acceptable. However, for a tool with 4 parameters, no annotations, and siblings like 'search-posts', it lacks context on behavioral traits (e.g., pagination defaults, error cases) and usage guidelines, making it incomplete for optimal agent decision-making.

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%, providing clear documentation for all parameters (e.g., 'hitsPerPage' for pagination, 'tags' for filtering). The description adds no additional parameter semantics beyond implying author-based retrieval via 'by a specific author', which aligns with the 'username' parameter. This meets the baseline score of 3 for high schema coverage.

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 tool's purpose with a specific verb ('Get') and resource ('posts by a specific author'), distinguishing it from siblings like 'get-user' (which retrieves user profiles) or 'search-posts' (which searches posts more broadly). However, it doesn't explicitly differentiate from 'search-posts-by-date' or 'get-latest-stories' in terms of author-specific filtering, leaving some ambiguity.

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 prerequisites (e.g., needing a valid username), exclusions (e.g., not for posts by multiple authors), or comparisons to siblings like 'get-user' (for author details) or 'search-posts' (for broader searches), leaving the agent to infer usage context.

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