Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd

Search Hacker News

hackernews_search_list
Read-only

Search Hacker News by keyword. Returns a list (use page/pageSize when paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoRestrict search to story URLs matching this URL substring. Can omit `query`.
pageNoZero-based page index (maximum 50 pages, up to 1,000 hits).
sortNoRanking mode. Default: `popularity`.
typeNoRestrict search results to a Hacker News content type. `ask_hn`: Ask HN posts (questions to the community). `show_hn`: Show HN posts (projects/work being shared). `launch_hn`: Launch HN posts (YC-affiliated company launches). Default: `all`.
limitNoHits per page. Must be one of 10, 20, 30, 50. Default: 20. Prefer this over `pageSize`.
queryNoFull-text search query. Required unless `frontPageOnly`, `author`, `domain`, or `url` is set.
authorNoRestrict results to items by this Hacker News username.
domainNoRestrict search to story URLs matching this domain (e.g. example.com). Can omit `query`.
prefixNoWhen true, enable prefix matching for query tokens.
pageSizeNoDeprecated alias for `limit`. When both are set, `limit` wins.
dateRangeNoCreation-time window. Default: `all`.
minPointsNoMinimum points/score filter.
searchAuthorNoWhen true, include author username in the searchable fields.
frontPageOnlyNoWhen true, restrict results to current front-page items. Allows omitting `query`.
typoToleranceNoEnable typo tolerance. Default: true.
searchStoryTextNoInclude story/comment text in searchable fields. Default: true. Set false to search title/URL only.

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the description adds little beyond that. 'Returns a list' is trivial, and the pagination hint is already fully specified in the schema. No additional behavioral traits (e.g., result format, error conditions, rate limits) are disclosed.

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 short sentences, front-loaded with the core purpose, and no unnecessary words. Every sentence earns its place, making it highly concise and easy to scan.

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

Completeness2/5

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

For a tool with 16 parameters and no output schema, the description is insufficient. It implies keyword-only search, but the tool supports filtering by author, domain, type, date range, and more. An agent relying on this description would miss the full capability and might incorrectly assume query is always required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with all 16 parameters documented. The description merely repeats keyword and pagination without adding any new meaning or clarifying parameter interplay (e.g., that query can be omitted when author/domain/url is set).

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 clearly states 'Search Hacker News by keyword', identifying the verb (search), resource (Hacker News), and a specific scope (keyword). This distinguishes it from the many other search tools for other platforms in the sibling list.

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?

The description gives no guidance on when to use this tool versus alternatives, no context, and no exclusions. It simply states the action without helping the agent decide when to prefer it over other Hacker News search or list tools.

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

All Social Fetch toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation5/5

Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.

Naming Consistency5/5

All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).

Tool Count2/5

The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.

Completeness4/5

The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.

Resources