Social Fetch

List Hacker News user comments

hackernews_user_comments_list

Read-only

List a Hacker News user's comments (newest first). Accepts a username. Returns a list (use page/pageSize when paginated).

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Zero-based page index (maximum 50 pages, up to 1,000 hits).
`trim`	No	Ignored if this tool does not support it.
`limit`	No	Hits per page (1–50). Default: 20. Prefer this over `pageSize`.
`offset`	No	Ignored if this tool does not support it.
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`pageSize`	No	Deprecated alias for `limit`. When both are set, `limit` wins.
`username`	Yes	Hacker News username (case-sensitive).
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`maxResults`	No	Ignored if this tool does not support it.
`max_results`	No	Ignored if this tool does not support it.
`conversation_id`	No	Echo 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.

Changed4 schema fields changedSep 21, 2026

addedInput schema / properties / maxResults

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / max_results

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / trim

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

Changed5 schema fields changedSep 5, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo 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.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "username"
-]New value: +[
+  "username",
+  "context",
+  "llm_model"
+]

Changed1 schema field changedAug 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedAug 4, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Hits per page (1–50). Default: 20. Prefer this over `pageSize`.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / pageSize / description

Previous value: -"Hits per page (1–50). Default: 20."New value: +"Deprecated alias for `limit`. When both are set, `limit` wins."

Changed1 schema field changedJul 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
AddedJul 26, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare read-only and open-world behavior, and the description adds useful operational facts: newest-first ordering, a list return shape, and pagination availability. It does not address edge cases like nonexistent usernames or rate limits, but that burden is lowered by the annotations.

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?

Three short clauses in a single sentence, front-loaded with the action and key resource, with no filler or repetition.

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 description conveys the core resource and result type, but for an 11-parameter tool it ignores the two required metadata parameters (context, llm_model) and leaves pagination guidance incomplete with respect to limit versus pageSize. The schema covers these details, so the description is adequate but not fully self-sufficient.

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

Parameters2/5

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

Schema coverage is 100%, so the description did not need to document parameters, but its 'use page/pageSize when paginated' instruction actively conflicts with the schema, which says pageSize is a deprecated alias and that limit is preferred. No parameter gets meaningful added semantics from the description.

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 uses a specific verb ('List') and resource ('a Hacker News user's comments'), and adds the ordering fact 'newest first'. It is clearly distinguishable from story-comment or submission tools via the word 'user's', though it never explicitly names or contrasts any alternative sibling.

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?

There is no guidance about when to choose this tool over alternatives such as hackernews_story_comments_list or hackernews_user_submissions_list, and no exclusion criteria. 'Accepts a username' only implies a prerequisite rather than explaining selection context.

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

All Social Fetch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

List Hacker News user comments

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources