HackerNews-Search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-postsA | Search HackerNews for stories, comments, and other content by keyword. Supports:
Basic Examples:
Advanced Filtering Examples:
Numeric Filter Operators: < (less than), <= (less than or equal), = (equal), >= (greater than or equal), > (greater than) Numeric Filter Fields: points, num_comments, created_at_i (Unix timestamp) Tag Syntax:
Returns paginated results with hits, total count, and page information. |
| get-front-pageA | Retrieve posts currently on the HackerNews front page. Returns stories sorted by HackerNews ranking algorithm. The front page typically contains the most popular and trending stories. Supports:
Examples:
Returns the same structure as search results with hits, pagination info, and metadata. |
| get-latest-postsA | Retrieve the most recent HackerNews posts sorted by date. Returns posts in chronological order (newest first), including all types of content unless filtered. Supports:
Examples:
Use this to monitor real-time HackerNews activity or find the newest content. |
| get-itemA | Retrieve detailed information about a specific HackerNews item by ID. Returns complete item details including the full nested comment tree. Use this to:
Features:
Examples:
Note: Large comment threads (>500 comments) may take 2-3 seconds to load due to nested fetching. Returns error if item doesn't exist or has been deleted. |
| get-userA | Retrieve public profile information for a HackerNews user. Returns user profile including karma, bio, and account creation date. Use this to:
Features:
Examples:
Username validation:
Returns error if user doesn't exist or username format is invalid. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: get-front-page retrieves front-page stories, get-item fetches specific items with comments, get-latest-posts gets recent posts chronologically, get-user retrieves user profiles, and search-posts performs keyword searches. The descriptions reinforce these unique roles, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern with hyphens (e.g., get-front-page, search-posts). The verbs are clear and descriptive (get, search), and the nouns specify the target resource (front-page, item, latest-posts, user, posts), creating a predictable and readable naming convention throughout the set.
With 5 tools, the set is well-scoped for a HackerNews search server, covering key functionalities like retrieving front-page content, specific items, recent posts, user profiles, and search. Each tool earns its place without redundancy, providing a focused and manageable interface for agents to interact with HackerNews data.
The tool surface is complete for a HackerNews search domain, offering comprehensive coverage: get-front-page and get-latest-posts handle curated and chronological views, get-item provides detailed item access, get-user covers user profiles, and search-posts enables advanced filtering. There are no obvious gaps, supporting a wide range of agent workflows without dead ends.