Skip to main content
Glama
Sign In
Product Hunt MCP Server

Product Hunt MCP Server

by Jing-yilin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_maker_group

Retrieve a maker group by ID and obtain cleaned data in TOON format.

Instructions

Get a maker group by ID. 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": {
      "id": "<id>"
    },
    "name": "get_maker_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMaker group ID
save_dirNoDirectory to save cleaned JSON data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions data cleaning and TOON format but fails to disclose that the 'save_dir' parameter implies writing to disk, a side effect. No info on auth, rate limits, or destructive potential.

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?

The description is two short sentences, front-loaded with the primary action. It is concise, though could potentially be merged into one sentence for even tighter structure.

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?

While the schema covers parameters, the description omits important context: what 'cleaned' means, what TOON format is, and that 'save_dir' writes to disk (a side effect). For a tool with a write parameter, this is inadequate.

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 the baseline is 3. The description adds mention of 'cleaned data in TOON format' but does not enhance the parameter descriptions beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 maker group by ID and returns cleaned data, which distinguishes it from sibling 'get_maker_groups' (plural) that likely retrieves multiple groups. However, it does not explicitly differentiate from other getter tools.

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 or when not to use it. No context is given about prerequisites or typical use cases.

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