RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Langchain4j] Enhance ToolSpecification Mapping

Enhance the mapping of tool information in langchain4j to include detailed parameters required for invoking a tool in JSON format, allowing users to understand what is needed and how to validate it.

Original Source

@@alan-atkinson | 0 pts | 3/12/2026

**Is your feature request related to a problem? Please describe.** not a problem per se - two enhancements. tangentially related to #3291 An mcp server issues a quite detailed list of the parameters required for invoking a tool in a JSON format. This lets you both tell (someone) what they actually need to invoke this tool and has instructions on validating anything that is provided for same. Sadly the tool information in langchain4j gets mapped to a ToolSpecification. It would be really easy to tell (someone) what's required to invoke this tool if you could serialize same. But it's not jackson compliant so it won't serialize and you (one) ends up either overriding swathes of the code as a workaround, writing a custom serializer, or calling the MCP server yourself with something like springs webclient and parsing either the json or the sse response manually. **Describe the solution you'd like** 1. Fix the ToolSpecification so it can be serialized to json without writing a custom

Discussion

Loading comments...