Skip to main content
Glama
mldsveda

PyScrappy

by mldsveda
OverviewSchemaRelated ServersScoreDiscussions
Python

search_hackernews

Search Hacker News for stories matching your query, returning titles, URLs, points, authors, and comment counts. Sort by relevance or date and filter by tags such as Show HN or Ask HN.

Instructions

Search Hacker News stories and return a list of matching story dicts, each with title, url, points, author (username), and num_comments (comment count).

Queries the public Hacker News search index (Algolia HN API) over the network; makes no local changes. Returns an empty list when nothing matches or the query is empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
byNoResult ordering; type: string; one of "relevance" or "date" ("date" sorts most recent first); example: "date"; default: "relevance".relevance
tagsNoAlgolia HN tag filter; type: string; common values "story", "comment", "show_hn", "ask_hn", "poll", "job"; example: "show_hn"; default: "story".story
queryYesSearch terms to match against story titles and text; type: string; example: "rust async runtime"; no default (required).
max_resultsNoMaximum number of stories to return; type: integer; example: 10; default: 20.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
countNo
errorsNo
scraperNo
source_urlsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.4.6
    • addedInput schema / properties / tags
      Added value: +{
+  "default": "story",
+  "description": "Algolia HN tag filter; type: string; common values \"story\", \"comment\", \"show_hn\", \"ask_hn\", \"poll\", \"job\"; example: \"show_hn\"; default: \"story\".",
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / by / description
      Previous value: -"\"relevance\" (default) or \"date\" (most recent first)."New value: +"Result ordering; type: string; one of \"relevance\" or \"date\" (\"date\" sorts most recent first); example: \"date\"; default: \"relevance\"."
    • changedInput schema / properties / max_results / description
      Previous value: -"Max stories to return (default 20)."New value: +"Maximum number of stories to return; type: integer; example: 10; default: 20."
    • changedInput schema / properties / query / description
      Previous value: -"Search query."New value: +"Search terms to match against story titles and text; type: string; example: \"rust async runtime\"; no default (required)."
  3. Changed20 schema fields changedv1.3.3
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / by / description
      Added value: +"\"relevance\" (default) or \"date\" (most recent first)."
    • removedInput schema / properties / by / title
      Removed value: -"By"
    • addedInput schema / properties / max_results / description
      Added value: +"Max stories to return (default 20)."
    • removedInput schema / properties / max_results / title
      Removed value: -"Max Results"
    • addedInput schema / properties / query / description
      Added value: +"Search query."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_hackernewsArguments"
    • removedOutput schema / $defs
      Removed value: -{
-  "ToolError": {
-    "description": "A non-fatal problem encountered while scraping.",
-    "properties": {
-      "message": {
-        "title": "Message",
-        "type": "string"
-      },
-      "url": {
-        "title": "Url",
-        "type": "string"
-      }
-    },
-    "required": [
-      "url",
-      "message"
-    ],
-    "title": "ToolError",
-    "type": "object"
-  }
-}
    • removedOutput schema / properties / count / title
      Removed value: -"Count"
    • removedOutput schema / properties / data / title
      Removed value: -"Data"
    • removedOutput schema / properties / errors / items / $ref
      Removed value: -"#/$defs/ToolError"
    • addedOutput schema / properties / errors / items / description
      Added value: +"A non-fatal problem encountered while scraping."
    • addedOutput schema / properties / errors / items / properties
      Added value: +{
+  "message": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / errors / items / required
      Added value: +[
+  "url",
+  "message"
+]
    • addedOutput schema / properties / errors / items / type
      Added value: +"object"
    • removedOutput schema / properties / errors / title
      Removed value: -"Errors"
    • removedOutput schema / properties / scraper / title
      Removed value: -"Scraper"
    • removedOutput schema / properties / source_urls / title
      Removed value: -"Source Urls"
    • removedOutput schema / title
      Removed value: -"ScrapeToolResult"
  4. Addedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Explicitly states 'makes no local changes' and discloses the network dependency on the Algolia HN API, plus the empty-list behavior. With no annotations present, the description carries the burden well, though it omits rate-limit or error details.

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?

Two sentences, front-loaded with the main action and output shape, and no redundant phrasing. Every sentence contributes meaningful information.

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 simple search tool with a rich schema and explicit output shape, the description covers the essentials: network usage, non-destructive behavior, and empty-list handling. It could mention rate limits or errors, but that is not critical given the simplicity.

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%, with every parameter having type, default, and example. The description adds no parameter-specific details beyond the schema, so the baseline of 3 is appropriate.

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?

Description opens with a specific verb 'Search' and resource 'Hacker News stories', and clearly specifies the output as a list of dicts with named fields (title, url, points, author, num_comments). This clearly distinguishes it from sibling search tools like search_github or search_images.

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?

States it queries the public Hacker News index over the network and returns an empty list for no matches/empty query, providing clear usage context. It does not explicitly mention alternatives or exclusions, but the tool's niche is unambiguous given the sibling list.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mldsveda/PyScrappy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server