Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hacker News user submissions

hackernews_user_submissions_list
Read-onlyIdempotent

List a Hacker News user's stories, polls, and jobs newest first; provide the username and use page/limit to paginate results.

Instructions

List a Hacker News user's stories, polls, and jobs (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_submissions_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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is fully covered and the description needn't restate it. What it does add beyond the annotations is useful: the 'newest first' ordering and the fact that the result is a list that becomes paginated. It stops short of anything about page limits or what happens past the pagination boundary.

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?

Two short sentences with the resource and ordering front-loaded and nothing wasted. 'Requires `username`' is mild redundancy against the required array, and the pagination hint trailing in parentheses is thin, but neither sentence bloats the definition.

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 endpoint with full schema coverage and no output schema, the description covers what is returned at a level of detail (item types plus ordering) that lets an agent call it correctly. The only gap is the deprecation-aware pagination guidance, which the description muddles instead of clarifying.

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 coverage is 100%, so the schema already documents all seven parameters including the context/llm_model/conversation_id meta-params and the limit-vs-pageSize deprecation. The description's only parameter remark, 'use page/pageSize when paginated', actually conflicts with the schema, which marks `pageSize` deprecated and says to prefer `limit` — a small but real misdirection.

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 stories, polls, and jobs') and adds a scope qualifier ('newest first'). The enumeration of item types implicitly separates it from hackernews_user_comments_list and hackernews_user_favorites_list, but it never names those siblings, so the agent must infer the boundary rather than being told it.

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?

Only a hard requirement is stated ('Requires `username`'), which is already in the schema's required list. There is no guidance on when to pick this over hackernews_user_comments_list, hackernews_user_favorites_list, or hackernews_search_list — the closest available alternatives — leaving selection to inference from the item-type list.

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