Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List a Hacker News feed

hackernews_feed_list
Read-onlyIdempotent

List Hacker News feeds by type (top, new, best, ask, show, or jobs) and paginate results to browse stories, discussions, or job posts.

Instructions

List a Hacker News feed by type (top, new, best, ask, show, or jobs). Requires feed. Returns a list (use page/pageSize when paginated).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feed": "<feed>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hackernews_feed_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYesHacker News feed: top, new, best, ask, show, or jobs.
pageNoZero-based page index (maximum 50 pages). Default: 0. Advance with `data.page.nextPage` when `hasMore` is true.
limitNoItems to hydrate per page (1–50). Default: 30. Prefer this over `pageSize`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
pageSizeNoDeprecated alias for `limit`. When both are set, `limit` wins.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds that results are paginated and come back as a list, but says nothing about rate limits, the required context/llm_model/conversation_id etiquette, or what an item looks like. It also endorses 'pageSize', which the schema marks as deprecated in favor of limit — a schema inconsistency rather than an annotation contradiction.

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

Conciseness4/5

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

Three short sentences with the resource and required parameter front-loaded and no filler. Slight waste in repeating the feed enum already given in the schema.

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?

For a read-only list tool with no output schema and full schema coverage, the description covers purpose, required input and pagination sufficiently. It stops short of explaining what a returned item contains or how paging interacts with the required conversation_id echo, but those gaps are largely filled by the schema.

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 fully documents all seven parameters including the deprecated pageSize and the hasMore/nextPage paging advice; the baseline is 3. The description only restates the feed enumeration and names page/pageSize, adding no meaning beyond the schema and mildly contradicting the deprecation note.

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 states a specific verb and resource (list a Hacker News feed) and enumerates the exact feed types (top, new, best, ask, show, jobs), so an agent knows the scope without opening the schema. It does not differentiate from close siblings such as hackernews_search_list or hackernews_jobs_who_is_hiring_list, even though the 'jobs' value overlaps with the latter.

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

Usage Guidelines3/5

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

Usage is only implied: the tool is for listing a named feed, and 'use page/pageSize when paginated' hints at paging. There is no explicit guidance on when to prefer this over search or the jobs-specific sibling, nor any prerequisite notes beyond 'requires feed', which the schema already enforces.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools