Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hacker News user comments

hackernews_user_comments_list
Read-onlyIdempotent

Fetch a Hacker News user's comments newest first by username to review their discussion history, with pagination for large result sets.

Instructions

List a Hacker News user's comments (newest first). Requires username. 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": {
      "username": "<username>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hackernews_user_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page index (maximum 50 pages, up to 1,000 hits).
limitNoHits per page (1–50). Default: 20. 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.
usernameYesHacker News username (case-sensitive).
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?

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only the ordering trait ('newest first') and a pagination note; it says nothing about what happens for a nonexistent or case-mismatched username or about rate limits on an open-world fetch.

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?

A single compact sentence with the resource and requirement front-loaded and no filler. The trailing 'use page/pageSize when paginated' clause is the one piece that does not clearly earn its place, since it duplicates and partially contradicts 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 operation with full schema coverage, rich annotations and no output schema, the description covers what the tool returns at a high level and how ordering works. The remaining gap is differentiation from the story-comments sibling, which is minor for this tool shape.

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 all seven parameters, including the unusual required context and llm_model fields, are already documented in the schema. The description's only parameter content steers toward pageSize, which the schema explicitly marks as a deprecated alias for limit — that advice adds no value and mildly conflicts with the schema's own preference.

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 gives a specific verb and resource ('List a Hacker News user's comments'), which separates it from story comments and user submissions by scope. It stops short of naming a sibling to route against, so an agent must infer the distinction from the resource noun alone.

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?

The only usage guidance is 'use page/pageSize when paginated', which is a parameter hint rather than a when-to-use rule. There is no statement about when to prefer this over hackernews_story_comments_list or hackernews_user_submissions_list, so the agent must infer that from the name.

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