Feature Request Harvester
Turn scattered "I wish it could" chatter into a ranked, evidence-backed feature backlog
https://apidirect.io/mcp?token=YOUR_API_KEY
Build me a ranked feature backlog of everything users wish {product} could do.
feature-request-harvester.
Any agent can also call get_skill(skill_id="feature-request-harvester") to pull these steps on demand.
What it does
Users rarely file feature requests — they vent them as wishes in passing. This skill mines wish-phrasing across communities and ranks each desired capability by how often it recurs and how strongly people feel about its absence.
Who it's for: Product managers and founders building a roadmap
Inputs
| Input | Required | Description | Example |
|---|---|---|---|
product |
Yes | Product or brand name to mine for unmet feature wishes | Notion |
How your agent runs it
-
1
search_reddit(query='{product} "i wish" OR "would love" OR "needs a"', sort_by=top, get_sentiment=true)Capture top wish-phrased posts; prioritize ones whose dominant_emotion is anticipation or sadness (felt gaps).
-
2
search_forums(query='{product} feature request OR missing OR "no way to"', time=year, get_sentiment=true)Pull niche power-user threads that name specific missing capabilities.
-
3
search_twitter(query='{product} "wish it could" OR "why cant {product}" OR "needs to add"', sort_by=relevance, get_sentiment=true)Add public X chatter and note the most-engaged wishes as demand signal.
-
4
search_reddit_comments(query='{product} lacks OR "doesnt support" OR workaround', sort_by=top, get_sentiment=true)Surface buried in-thread complaints and the workarounds people resort to, then cluster all four sources into themes.
Tools used
The full playbook
This is exactly what the MCP returns to your agent (via the feature-request-harvester prompt or get_skill tool), with your inputs filled in.
SKILL: Feature Request Harvester
Users rarely file feature requests — they vent them as wishes in passing. This skill mines wish-phrasing across communities and ranks each desired capability by how often it recurs and how strongly people feel about its absence.
You are running this skill on API Direct via its MCP tools. Execute the steps below yourself by calling the named tools in order — values in <angle brackets> come from a previous step. Then deliver the result described at the end.
INPUTS:
- product (required): <product — ASK THE USER>
STEPS:
1. Tool `search_reddit` — search_reddit(query='<product> "i wish" OR "would love" OR "needs a"', sort_by=top, get_sentiment=true)
Capture top wish-phrased posts; prioritize ones whose dominant_emotion is anticipation or sadness (felt gaps).
2. Tool `search_forums` — search_forums(query='<product> feature request OR missing OR "no way to"', time=year, get_sentiment=true)
Pull niche power-user threads that name specific missing capabilities.
3. Tool `search_twitter` — search_twitter(query='<product> "wish it could" OR "why cant <product>" OR "needs to add"', sort_by=relevance, get_sentiment=true)
Add public X chatter and note the most-engaged wishes as demand signal.
4. Tool `search_reddit_comments` — search_reddit_comments(query='<product> lacks OR "doesnt support" OR workaround', sort_by=top, get_sentiment=true)
Surface buried in-thread complaints and the workarounds people resort to, then cluster all four sources into themes.
DELIVER: A ranked feature backlog where each requested capability is scored by mention frequency across platforms and emotional intensity, with linked source quotes.
Note: each underlying tool call is billed at its normal endpoint price; get_sentiment adds a small per-page surcharge. Page through results as needed but stop once you have enough to deliver the outcome.