datasets_producthunt_trends_search
Search the Product Hunt trends dataset. Returns aggregate Product Hunt launch trends from the dataset id enum value producthunt-trends. Aggregate-only: each row is a category-over-time cell (a topic, optionally within a calendar period), reporting launch count, total and average upvotes, average ...
This record as markdown: /tools/crawlora-mcp/datasets-producthunt-trends-search.md
What datasets_producthunt_trends_search does on Crawlora
AI agents call datasets_producthunt_trends_search to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number, defaults to 1 |
sort | string | — | Sort enum: period_desc, period_asc, launch_count_desc, sum_votes_desc |
topic | string | — | Exact topic-slug filter, e.g. artificial-intelligence, max 128 characters |
group_by | string | — | Aggregate cell dimension enum: topic_month, topic_year, topic. Defaults to topic_month |
min_votes | integer | — | Minimum product upvotes, 0 or greater |
page_size | integer | — | Page size, defaults to 20 and maxes at 100; page * page_size must be <= 10000 |
min_launches | integer | — | Minimum launches per cell; raises the small-cell suppression floor (never lowered below the built-in minimum) |
launched_after | string | — | Lower bound on first-launch date, an ISO-8601 date (YYYY-MM-DD) |
launched_before | string | — | Upper bound on first-launch date, an ISO-8601 date (YYYY-MM-DD) |
Parameters from the server's own tool schema.
Why datasets_producthunt_trends_search is rated Low
Even though datasets_producthunt_trends_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs datasets_producthunt_trends_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For datasets_producthunt_trends_search, this is the rule to start with:
datasets_producthunt_trends_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every datasets_producthunt_trends_search call is checked against it from then on.
Questions about datasets_producthunt_trends_search
Search the Product Hunt trends dataset. Returns aggregate Product Hunt launch trends from the dataset id enum value producthunt-trends. Aggregate-only: each row is a category-over-time cell (a topic, optionally within a calendar period), reporting launch count, total and average upvotes, average rating and the top product — never an individual product record. Thin cells are suppressed. group_by enum: topic_month, topic_year, topic. Sort enum: period_desc, period_asc, launch_count_desc, sum_votes_desc. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
datasets_producthunt_trends_search accepts 9 parameters: page, sort, topic, group_by, min_votes, page_size, min_launches, launched_after, launched_before. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for datasets_producthunt_trends_search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Crawlora. Nothing to install.
datasets_producthunt_trends_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the datasets_producthunt_trends_search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for datasets_producthunt_trends_search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
datasets_producthunt_trends_search is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue