Social Fetch

List Who is Hiring jobs

hackernews_jobs_who_is_hiring_list

Read-only

List top-level jobs from the monthly Hacker News Who is Hiring thread (latest thread, or a YYYY-MM month). Returns a list (use page/pageSize when paginated).

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Zero-based page index of top-level hiring comments.
`trim`	No	Ignored if this tool does not support it.
`limit`	No	Job rows per page (1–50). Default: 20. Prefer this over `pageSize`.
`month`	No	Calendar month (YYYY-MM) to pin a Who is Hiring thread. Default: latest thread.
`offset`	No	Ignored if this tool does not support it.
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`pageSize`	No	Deprecated alias for `limit`. When both are set, `limit` wins.
`llm_model`	Yes	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.
`maxResults`	No	Ignored if this tool does not support it.
`max_results`	No	Ignored if this tool does not support it.
`conversation_id`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 21, 2026

addedInput schema / properties / maxResults

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / max_results

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / trim

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

Changed5 schema fields changedSep 5, 2026

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"
+}

addedInput schema / required

Added value: +[
+  "context",
+  "llm_model"
+]

Changed1 schema field changedAug 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedAug 4, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Job rows per page (1–50). Default: 20. Prefer this over `pageSize`.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / pageSize / description

Previous value: -"Job rows per page (1–50). Default: 20."New value: +"Deprecated alias for `limit`. When both are set, `limit` wins."

Changed1 schema field changedJul 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
AddedJul 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, lowering the bar. The description adds a pagination hint ('use page/pageSize when paginated'), which is useful, but it suggests pageSize despite the schema marking pageSize as a deprecated alias for limit. This minor inconsistency slightly undermines the behavioral guidance.

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?

A single, concise sentence that front-loads the core purpose and includes a short parenthetical for pagination. No filler, but the deprecated 'page/pageSize' reference costs it a point for slight inaccuracy.

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

Completeness3/5

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

For a simple read-only list tool, it is mostly adequate: it states the resource, optional month, and return type. Gaps remain: no description of the list item structure, no clarification on default limit or pagination behavior, and the pageSize/limit ambiguity could mislead. With no output schema, a bit more detail on return shape would make it complete.

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%, so the schema fully documents the parameters. The description adds no semantic value beyond what the schema already provides; the month format and pagination details are already in the schema. Baseline 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?

Clearly specifies a unique action ('List top-level jobs') and resource ('monthly Hacker News Who is Hiring thread'), distinguishing it from siblings like hackernews_story_comments_list or search tools. The tool's scope (latest or specific month) is immediately identifiable.

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 implies usage via 'latest thread, or a YYYY-MM month', but provides no explicit when-to-use or when-not-to-use guidance relative to alternative HN tools. There is no mention of exclusions or preferred scenarios, leaving the agent to infer.

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

All Social Fetch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

List Who is Hiring jobs

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources