Skip to main content
Glama
Sign In
Product Hunt MCP Server

Product Hunt MCP Server

by Jing-yilin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_topic

Retrieve a Product Hunt topic by ID or slug. Returns cleaned data in TOON format for integration.

Instructions

Get a Product Hunt topic by ID or slug. Returns cleaned data in TOON format.

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": "get_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoTopic ID
slugNoTopic slug
save_dirNoDirectory to save cleaned JSON data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It mentions 'cleaned data in TOON format' but does not explain what 'cleaned' means, what TOON format entails, or any side effects. No details on auth, rate limits, or error handling.

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?

The description is one sentence, 14 words, front-loaded, with no fluff. Every word adds value.

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?

Given 3 parameters, no output schema, and no annotations, the description is too brief. It lacks details on return values, error conditions, authentication requirements, and the meaning of 'cleaned data' and 'TOON format'.

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 coverage is 100%, so baseline is 3. The description adds no new meaning beyond the schema; it just restates that ID or slug can be used. The save_dir parameter is not elaborated on.

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 the tool gets a Product Hunt topic by ID or slug, using specific verbs and resource. It distinguishes from sibling tools like get_topics (plural, likely lists topics) and other get_* tools.

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 when you have an ID or slug, but does not specify when to avoid using the tool or mention alternatives. No explicit guidance on context or prerequisites.

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

Deploy Server

Other Tools