Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hacker News user favorites

hackernews_user_favorites_list
Read-onlyIdempotent

Fetch a Hacker News user's favorite items by username, using page numbers to retrieve paginated results.

Instructions

List favorites for a Hacker News user by username. Requires username. Returns a list (use page 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_favorites_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based HTML favorites page number. Default: 1. Each page bills 1 credit.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only that the result is a list and that pagination is available, without covering the credit cost per page, ordering, or what happens with a nonexistent user — modest added value on top of 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.

Conciseness4/5

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

Three short sentences with the core action front-loaded and no filler prose. 'Requires `username`' is largely redundant with the schema's required list and the page hint is terse, but nothing bloats the definition.

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?

For a five-parameter tool with three required plumbing parameters and no output schema, the description does the minimum: it says a list is returned and points to page for pagination. It omits the per-page credit cost, ordering of results, and error behavior for unknown users, leaving the agent to rely entirely on schema text.

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%, including detailed notes for page (one-based HTML page, default 1, 1 credit per page), username (case-sensitive), and the context/llm_model/conversation_id plumbing parameters. The description repeats the required-username fact and gestures at page without adding syntax or semantics beyond the schema, 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?

The description states a specific verb and resource ('List favorites for a Hacker News user') scoped by username, which is clearly distinct from the sibling list tools for comments and submissions. It stops short of naming those siblings to sharpen the distinction, so it lands at clear-but-not-differentiating.

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 when-to-use guidance: nothing says when to pick this over hackernews_user_comments_list or hackernews_user_submissions_list, nor any prerequisite such as the user needing public favorites. The only hint is 'use page when paginated', which is a paging note rather than tool-selection guidance.

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