Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Product Hunt

product_hunt_search_list
Read-onlyIdempotent

Search Product Hunt products, users, posts, topics, and categories by query to find relevant listings and profiles; use cursor pagination to retrieve more results.

Instructions

Search Product Hunt products, users, posts, topics and categories, cursor-paged. Requires query. Returns a list (use cursor when paginated).

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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "product_hunt_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoWhat to search: `all` (default), `product`, `user`, `post`, `topic` or `category`.
queryYesRequired. What to search for, e.g. `notion` or `ai agents`.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same endpoint and filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds that results are cursor-paged and returned as a list, but says nothing about result caps, ordering, or rate limits. Useful but modest added context beyond the structured fields.

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 short sentences, front-loaded with what is searched, followed by the required parameter and return shape. No filler or redundancy.

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 6-parameter search tool with no output schema, the description covers the resource scope, the required input, and the return/paging shape. The analytics and conversation-tracking parameters are fully explained in the schema, so nothing critical is missing, though a note on when to choose search over the entity-specific list tools would complete it.

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%, including a fully documented enum for `type` and detailed cursor semantics tied to `page.nextCursor`. The description only restates that `query` is required and the cursor is for pagination, adding no meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Search Product Hunt products, users, posts, topics and categories') and adds the paging characteristic. It is clearly distinguishable from the *_get and *_list siblings by being a multi-entity search, though it never explicitly contrasts itself with the entity-specific list 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?

Provides a precondition ('Requires `query`') and a paging hint ('use cursor when paginated'), which implies usage. It gives no guidance on when to prefer this cross-entity search over siblings like product_hunt_posts_list or product_hunt_topics_list, and no exclusions.

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