Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd

List a Hacker News feed

hackernews_feed_list
Read-only

List a Hacker News feed by type (top, new, best, ask, show, or jobs). Accepts a feed name. Returns a list (use page/pageSize when paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedYesHacker News feed: top, new, best, ask, show, or jobs.
pageNoZero-based page index (maximum 50 pages). Default: 0. Advance with `data.page.nextPage` when `hasMore` is true.
limitNoItems to hydrate per page (1–50). Default: 30. Prefer this over `pageSize`.
contextYesDescribe the user's underlying goal in one sentence — not the tool you are calling.
pageSizeNoDeprecated alias for `limit`. When both are set, `limit` wins.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

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

  1. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
+  "type": "string"
+}
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}
    • addedInput schema / properties / llm_model
      Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "feed"
-]New value: +[
+  "feed",
+  "context",
+  "llm_model"
+]
  2. 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"
  3. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Items to hydrate per page (1–50). Default: 30. Prefer this over `pageSize`.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / pageSize / description
      Previous value: -"Items to hydrate per page (1–50). Default: 30."New value: +"Deprecated alias for `limit`. When both are set, `limit` wins."
  4. Changed4 schema fields changed
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "Maximum items to hydrate (1–50). Default: 30.",
-  "maximum": 50,
-  "minimum": 1,
-  "type": "integer"
-}
    • removedInput schema / properties / offset
      Removed value: -{
-  "description": "Zero-based offset into the official feed id list.",
-  "maximum": 500,
-  "minimum": 0,
-  "type": "integer"
-}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Zero-based page index (maximum 50 pages). Default: 0. Advance with `data.page.nextPage` when `hasMore` is true.",
+  "maximum": 49,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / pageSize
      Added value: +{
+  "description": "Items to hydrate per page (1–50). Default: 30.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}
  5. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  6. Added

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already covering side effects and world closure, the description adds useful behavioral context by stating it returns a list and that pagination is supported. It does not describe item shape or rate limits, but the annotation coverage lowers the bar.

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?

The description is short, front-loaded, and easy to parse. It loses a point because 'Accepts a feed name' is largely redundant with the first clause and the title, adding slight verbosity without new 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?

The rich schema covers required params, defaults, max values, deprecated aliases, and conversation sequencing, so the description need not repeat those. It correctly states the output kind (a list) and pagination approach. It is not a 5 because with no output schema, the returned item shape is left to inference.

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%, and the schema already explains each parameter including enums, defaults, maximums, deprecated aliases, and pagination mechanics. The description's 'Accepts a feed name' and 'use page/pageSize' add no meaningful semantics beyond the schema, so the baseline of 3 applies.

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 states a specific verb ('List') and resource ('Hacker News feed') and enumerates the valid feed types (top, new, best, ask, show, jobs), making it clear and distinct from sibling tools like hackernews_item_get or hackernews_search_list.

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

Usage Guidelines3/5

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

The description gives a clear context for what the tool lists and provides pagination guidance ('use page/pageSize when paginated'), but it does not explicitly say when to choose this over alternatives such as hackernews_search_list or hackernews_story_comments_list. The usage is implied rather than contrasted.

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