Skip to main content
Glama

Hacker News search

hackernews_search
Read-only

Hacker News Search & Stories: full-text search of Hacker News stories or comments (HN Search by Algolia). Per hit the title, text, author, points, comment count, linked URL, time and item URL in the shared social schema; next_cursor gives the next page. Tech news, launches and developer discussion for market and competitor research. Bad input is free; not found or no match is not charged. Price: $0.01 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "q": "<q>"
    },
    "name": "hackernews_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch text (1-200 characters).
typeNostory or comment. Default story.
limitNoResults per page, 1-20. Default 20.
cursorNonext_cursor of the previous page (a page number).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Well beyond the annotations, it discloses the per-hit return fields (title, text, author, points, comment count, linked URL, time, item URL) and that next_cursor paginates. Critically, it states the paid model: bad input is free, not-found or no-match is not charged, and $0.01 per successful call over x402 (USDC on Base) passed in _meta['x402/payment']. That payment prerequisite is behavior the readOnly/openWorld annotations cannot convey. The only gap is that it does not say whether the payment must be attached on every call or how to obtain payment metadata, which leaves an invocation-level ambiguity for a paid endpoint.

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?

It is front-loaded: purpose, then return shape, then use case, then pricing, so the agent gets the essential facts first. The phrasing is dense, though; the return-field list and the payment sentence are both long run-ons that mix response schema, billing and transport in one breath. Everything roughly earns its place, but it would read better split into shorter sentences.

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?

With no output schema, the description carries the return-value burden itself, and it does so by enumerating the fields per hit and naming the pagination cursor. Payment mechanics are also covered, which is unusual diligence. What's missing for a paid, open-world search endpoint is anything about failure modes or result ordering/relevance, leaving a small completeness gap.

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 four parameters (q, type, limit, cursor) are already documented in the schema, and the baseline is 3. The description adds only that next_cursor yields the next page, mapping that response field onto the cursor parameter, while q, type and limit are not discussed. That is a useful but small increment over structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: full-text search of Hacker News stories or comments via Algolia. It is unambiguous against the only close sibling, hackernews_thread (which retrieves a thread rather than searching), and against the other platform search tools. An agent can pick this tool from the name plus the first clause alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete use context: technology news, product launches and developer discussion for market and competitor research. That tells the agent when this source is appropriate relative to, say, general social search. It stops short of explicit exclusions or naming the alternative tool to use for thread-level or non-HN retrieval, so it sits at a clear-context-but-no-routing 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.