Find people asking for a service
find_buying_intentUse this when the user sells a service and wants public posts that ask for it, such as "who is asking for an SEO audit?" or "which companies on Hacker News are hiring for MCP work?". Pass service, for example {"service": "SEO audit"}, and optionally keywords, sources, lookback_days (7 to 365, default 30) and limit (1 to 15, default 10). Returns Hacker News posts, company posts from the newest "Who is hiring?" thread, GitHub issues and Stack Exchange posts, each with link, date, short quote, 0 to 100 intent score, label, reason, reply_angle and lead_source, by plain rules, no AI model. Use this, not weekly_brief, for a lookback other than 7 days or a set limit. Not for funded companies (use find_buyer_signals) or who wrote a post. A lead to read, not a sure sale. No usernames or contact details; Reddit is not searched. Free, no key: 4 lookups a day per network, shared with weekly_brief, reset at 00:00 UTC; a repeat within 6 hours comes from the cache and counts nothing.
Example tool call
This call uses example arguments supplied in the tool’s input schema.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"service": "SEO audit",
"lookback_days": 30
},
"name": "find_buying_intent"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many posts to return (default 10) | |
| service | Yes | The service you sell, not a company or person. Example call: {"service": "SEO audit"}. "alternative" alone, with no keywords, finds asks to replace any tool. Also try the person form (bookkeeper) | |
| sources | No | Which public sources to read: hackernews (comments and Ask HN), hn_hiring (company posts in the newest monthly Hacker News "Who is hiring?" thread), github (open and closed issues) and stackexchange; also job_changes (SEC 8-K officer changes that name a former customer, needs former_customers) and partners (WordPress.org plugin listings in the service's space, as partner leads). Default is the first four, plus job_changes when former_customers is given. Leave one out to skip it, for example stackexchange when it is rate limited | |
| keywords | No | Optional extra words a post must also contain, such as "shopify" or "small business" (up to 5). Every keyword must appear in a post, so a long list returns little. Leave it out for a first look and add one word only to narrow | |
| lookback_days | No | How many days of posts to read (default 30). This is 7 to 365, not the 1 to 60 of find_buyer_signals or the 30 to 365 of stack_pains | |
| former_customers | No | Up to 3 companies that were your customers, such as ["Salesforce"]: company names, never people. job_changes finds US public companies whose officer-change filings name them, a hint that someone you served moved there |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | Yes | ||
| as_of | Yes | ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch. | |
| notice | Yes | What a score does and does not mean. Pass it on | |
| Yes | |||
| source | Yes | Who the data comes from, to cite and to check it against. | |
| status | Yes | ok: posts found. no_data: no post asked for the service; message says what to try. unavailable: no source could be read; message says whether to retry or skip stackexchange | |
| window | Yes | ||
| dropped | Yes | Posts left out: seller posts and posts that ask for nothing | |
| message | No | The next step when status is not ok, a source was skipped or there are fewer than 3 results: the sources searched, then a longer lookback_days, the person form of the service, a source that fits and was not read, or leaving stackexchange out of sources | |
| results | Yes | ||
| service | Yes | ||
| how_scored | Yes | The scoring rules, so the user can see why a post scored as it did | |
| posts_read | Yes | Posts read from all sources | |
| attribution | Yes | CC BY-SA attribution for Stack Exchange text, or a line saying the answer holds none | |
| intent_count | Yes | Posts labelled intent | |
| sources_used | Yes | Sources read for this answer | |
| company_leads | No | Filings and listings found by job_changes and partners; they are companies, not posts, so posts_read leaves them out | |
| complaint_count | Yes | Posts labelled casual_complaint | |
| untrusted_source | Yes | ||
| posts_about_service | Yes | Posts that name the service | |
| sources_unavailable | Yes | Sources that could not be read and are missing from the answer |