Skip to main content
Glama
Sign In
Product Hunt MCP Server

Product Hunt MCP Server

by Jing-yilin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_user_voted_posts

Retrieve posts upvoted by a specific Product Hunt user to analyze their voting activity.

Instructions

Get posts upvoted by a user. Returns cleaned data in TOON format.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "get_user_voted_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesUsername
firstNoNumber of posts (default: 10)
afterNoCursor for pagination
save_dirNoDirectory to save cleaned JSON data
max_itemsNoMax items (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It mentions 'cleaned data in TOON format' but does not explain side effects like file saving via save_dir parameter, auth requirements, or pagination behavior. Minimal disclosure beyond the basic action.

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 extremely concise with two short sentences. No redundant information, every word adds value. Front-loaded with the main purpose.

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 the complexity (5 parameters, no output schema, no annotations), the description is incomplete. It fails to explain the purpose of save_dir (a side effect), the pagination mechanism (first, after), or the return format's structure. More detail is needed for effective use.

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?

All 5 parameters have descriptions in the input schema, so schema coverage is 100%. The description adds no extra meaning beyond what the schema already provides, so baseline score of 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?

The description clearly states 'Get posts upvoted by a user,' specifying the verb and resource. It distinguishes from sibling tools like get_user_posts and get_posts by focusing on upvoted posts.

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 provides no guidance on when to use this tool versus alternatives, such as get_user_posts for all user posts or search_posts for broader queries. No explicit when-not or context is given.

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