Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hacker News story comments

hackernews_story_comments_list
Read-onlyIdempotent

Fetch paginated comment trees for a Hacker News story by ID to review discussion threads and continue through results with a cursor.

Instructions

List comments on a Hacker News story by id. Requires id. Returns a list (use cursor 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": {
      "id": "<id>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hackernews_story_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesHacker News story id whose comment tree should be returned.
limitNoMaximum comment nodes to return in this page (1–100). Default: 50.
cursorNoOpaque continuation cursor from a previous response. Omit for the first page.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds only that the result is a list with cursor-based pagination; it says nothing about comment tree depth/flattening, ordering, or whether child comments are included — meaningful gaps for a comment-tree tool.

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, front-loaded with the core action, with no filler. 'Requires `id`' mildly duplicates the schema's required list, but the brevity is appropriate for the tool's simplicity.

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?

The tool is a read-only paginated list with full schema coverage and no output schema, so the description needn't explain return fields. However, 'Returns a list' leaves the shape of a comment node (text, author, depth, children) undefined and there is no output schema to compensate.

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% and every parameter (id, limit, cursor, context, llm_model, conversation_id) is documented in the schema. The description restates only `id` and cursor, adding no semantics beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb and resource with its parent scope: 'List comments on a Hacker News story by id.' That separates it from sibling comment tools like hackernews_user_comments_list (user-scoped) and hackernews_comment_context_get (single comment), though it never names those alternatives explicitly.

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?

Gives one concrete usage rule — 'use cursor when paginated' — which is real operational guidance. It offers no when-to-use versus hackernews_comment_context_get or hackernews_item_get, and no exclusions, so routing between the story-level and comment-level tools is left to inference.

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