Skip to main content
Glama

Hackernews

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Item

get_item
Read-onlyIdempotent

Fetch a Hacker News story or comment by ID (e.g., "42153809"). Returns full text, score, author, timestamp, and child replies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe numeric Hacker News item ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
byNoAuthor username
idYesHN item ID
urlNoItem URL
deadNoWhether item is dead/removed
kidsNoArray of child item IDs
textNoItem text content
timeNoUnix timestamp of item posting
typeNoItem type (story, comment, etc.)
scoreNoItem score/points
titleNoItem title
parentNoParent item ID
deletedNoWhether item is deleted
descendantsNoNumber of child comments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "id": 42153809
-  },
-  {
-    "id": 38000000
-  }
-]New value: +[
+  {
+    "id": 8863
+  },
+  {
+    "id": 38000000
+  }
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "by": {
+      "description": "Author username",
+      "type": "string"
+    },
+    "dead": {
+      "description": "Whether item is dead/removed",
+      "type": "boolean"
+    },
+    "deleted": {
+      "description": "Whether item is deleted",
+      "type": "boolean"
+    },
+    "descendants": {
+      "description": "Number of child comments",
+      "type": "number"
+    },
+    "id": {
+      "description": "HN item ID",
+      "type": "number"
+    },
+    "kids": {
+      "description": "Array of child item IDs",
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "parent": {
+      "description": "Parent item ID",
+      "type": "number"
+    },
+    "score": {
+      "description": "Item score/points",
+      "type": "number"
+    },
+    "text": {
+      "description": "Item text content",
+      "type": "string"
+    },
+    "time": {
+      "description": "Unix timestamp of item posting",
+      "type": "number"
+    },
+    "title": {
+      "description": "Item title",
+      "type": "string"
+    },
+    "type": {
+      "description": "Item type (story, comment, etc.)",
+      "type": "string"
+    },
+    "url": {
+      "description": "Item URL",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 42153809
+  },
+  {
+    "id": 38000000
+  }
+]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior. The description adds useful behavioral context by specifying what is returned (full text, score, author, timestamp, child replies), going beyond the structured 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?

The description is two short sentences with no filler. The primary operation and scope are front-loaded, and the return-value summary is informative without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup tool with a rich output schema and safety-relevant annotations, the description covers all essentials: what to pass, what it fetches, and what the response contains. Nothing critical is missing for an agent to invoke it correctly.

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?

The schema already fully documents the single parameter as 'The numeric Hacker News item ID' with 100% coverage. The description adds an example and clarifies that the item can be a story or comment, but does not fundamentally enhance the parameter meaning beyond the schema.

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 uses a clear action verb ('Fetch'), names the exact resource ('Hacker News story or comment'), and scopes it by ID. Listing the returned fields further disambiguates it from list/search tools among the siblings.

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?

The description clearly signals when to use this tool: when you already have a specific Hacker News item ID and want its details. It does not explicitly mention alternatives like search_hn or get_stories, but the by-ID framing provides clear context without exclusions.

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

All Hackernews toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources