Skip to main content
Glama
Sign In
Product Hunt MCP Server

Product Hunt MCP Server

by Jing-yilin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_viewer

Retrieve authenticated user information from Product Hunt, returning cleaned data in TOON format.

Instructions

Get authenticated user info. 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_viewer"
  }
}

Input Schema

NameRequiredDescriptionDefault
save_dirNoDirectory to save cleaned JSON data

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?

The description mentions 'Returns cleaned data in TOON format' without explaining TOON or side effects. The optional save_dir parameter suggests file writing, but the description does not clarify behavior when omitted or if authentication is needed. No annotations compensate.

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?

Two sentences with no unnecessary words. Efficiently communicates the core purpose and a notable output detail.

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?

Missing output schema, error conditions, authentication hints, and details on return structure. Given the tool's simplicity, more context would help an agent use it correctly.

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% (save_dir described). The description adds no extra meaning beyond the schema, but matches the baseline for full coverage.

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's purpose: 'Get authenticated user info.' This distinguishes it from sibling tools like get_user (which requires a user ID) and others that retrieve collections or 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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools include many get_* functions, but the description does not explain why one would choose get_viewer over get_user or others.

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