Skip to main content
Glama
Substack, B2B Churn & Lead MCP Server

Substack, B2B Churn & Lead MCP Server

by willowswt

search_hn_producthunt_launches

Read-onlyIdempotent

Search recent Show HN, Ask HN, and Product Hunt startup launches by keyword to return product titles, founder handles, URLs, engagement points/comments, and discussion threads for lead discovery.

Instructions

Search recent Show HN, Ask HN, and Product Hunt startup launches by keyword (query), returning product title, founder handle, startup URL, engagement points/comments, and discussion thread.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_hn_producthunt_launches"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword filter (e.g. 'mcp', 'ai agent', 'devtools', 'crm').
maxResultsNoMaximum launches to return (1-25, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered by structured data. The description's contribution beyond that is the return payload (title, founder handle, URL, points/comments, thread), which is genuinely useful given no output schema exists, but it says nothing about ordering, pagination, the length of the 'recent' window, or rate/openauth constraints of an open-world search.

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?

A single front-loaded sentence: verb, resource, scoping parameter, then return fields in priority order. No filler, no restatement of the title, and the parenthetical backtick reference to `query` is a clean tie to the schema.

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?

For a two-parameter read-only search with no output schema, the description covers what is searched, how it is filtered, and what comes back — enough for an agent to call it correctly. The remaining gap is the undefined 'recent' window and absence of any result-count/ordering expectation, which is a minor omission rather than a blocker.

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 both `query` and `maxResults` are already documented with examples and a range. The description references `query` as a keyword filter but adds no syntax, matching behavior, or guidance beyond what the schema states, leaving `maxResults` unmentioned. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (Search) against a specific and unusual resource (Show HN / Ask HN / Product Hunt startup launches) and enumerates the returned fields. The resource is plainly distinct from every sibling tool (Substack newsletters, bio-link emails, company website contacts, Shopify churn reviews), so an agent can select it without opening the schema.

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?

Usage is implied by 'Search recent ... by keyword', which tells the agent this is keyword-driven discovery over a recent window, but there is no explicit when-to-use/when-not framing and no alternative tool is named or ruled out. The word 'recent' also caps scope without defining it.

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