Skip to main content
Glama

Buyer Signals

Find people asking for a service

find_buying_intent
Read-onlyIdempotent

Use 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

NameRequiredDescriptionDefault
limitNoHow many posts to return (default 10)
serviceYesThe 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)
sourcesNoWhich 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
keywordsNoOptional 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_daysNoHow 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_customersNoUp 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

NameRequiredDescriptionDefault
noteYes
as_ofYesISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.
noticeYesWhat a score does and does not mean. Pass it on
redditYes
sourceYesWho the data comes from, to cite and to check it against.
statusYesok: 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
windowYes
droppedYesPosts left out: seller posts and posts that ask for nothing
messageNoThe 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
resultsYes
serviceYes
how_scoredYesThe scoring rules, so the user can see why a post scored as it did
posts_readYesPosts read from all sources
attributionYesCC BY-SA attribution for Stack Exchange text, or a line saying the answer holds none
intent_countYesPosts labelled intent
sources_usedYesSources read for this answer
company_leadsNoFilings and listings found by job_changes and partners; they are companies, not posts, so posts_read leaves them out
complaint_countYesPosts labelled casual_complaint
untrusted_sourceYes
posts_about_serviceYesPosts that name the service
sources_unavailableYesSources that could not be read and are missing from the answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / attribution / description
      Previous value: -"CC BY-SA attribution for Stack Exchange text"New value: +"CC BY-SA attribution for Stack Exchange text, or a line saying the answer holds none"
    • addedOutput schema / properties / company_leads
      Added value: +{
      +  "description": "Filings and listings found by job_changes and partners; they are companies, not posts, so posts_read leaves them out",
      +  "type": "integer"
      +}
    • changedOutput schema / properties / message / description
      Previous value: -"The next step when status is not ok or a source was skipped, such as a longer lookback_days, the person form of the service, or leaving stackexchange out of sources"New value: +"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"
    • addedOutput schema / properties / results / items / properties / company
      Added value: +{
      +  "description": "The company: for hn_hiring the one the post names in its first line, for job_changes the filer, for partners the plugin",
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / properties / quote / description
      Previous value: -"A quote of the ask under 15 words; for job_changes the filer and the former customer it names, for partners the listing's own summary"New value: +"A quote of the ask under 15 words; for hn_hiring the first whole sentence that names the service, else the clauses that name it with … where cut, else the post's first line; for job_changes the filer and the former customer it names, for partners the listing's own summary"
    • addedOutput schema / properties / results / items / properties / role
      Added value: +{
      +  "description": "hn_hiring: the role the post names in its first line, when it names one",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / stack
      Added value: +{
      +  "description": "hn_hiring: products and languages the post names, such as Python or AWS, in the order named",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed13 schema fields changed
    • addedInput schema / properties / former_customers
      Added value: +{
      +  "description": "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",
      +  "items": {
      +    "maxLength": 60,
      +    "minLength": 2,
      +    "type": "string"
      +  },
      +  "maxItems": 3,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / properties / sources / description
      Previous value: -"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. Default is all four. Leave one out to skip it, for example stackexchange when it is rate limited"New value: +"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"
    • changedInput schema / properties / sources / items / enum
      Previous value: -[
      -  "hackernews",
      -  "hn_hiring",
      -  "github",
      -  "stackexchange"
      -]New value: +[
      +  "hackernews",
      +  "hn_hiring",
      +  "github",
      +  "stackexchange",
      +  "job_changes",
      +  "partners"
      +]
    • changedInput schema / properties / sources / maxItems
      Previous value: -4New value: +6
    • changedOutput schema / properties / results / items / properties / date / description
      Previous value: -"Day the post was made (YYYY-MM-DD)"New value: +"Day the post or filing was made, or the listing last updated (YYYY-MM-DD)"
    • addedOutput schema / properties / results / items / properties / label / description
      Added value: +"intent or casual_complaint for a post; job_change for an officer change naming a former customer; partner_fit for a partner listing"
    • changedOutput schema / properties / results / items / properties / label / enum
      Previous value: -[
      -  "intent",
      -  "casual_complaint"
      -]New value: +[
      +  "intent",
      +  "casual_complaint",
      +  "job_change",
      +  "partner_fit"
      +]
    • changedOutput schema / properties / results / items / properties / lead_source / description
      Previous value: -"Which buying-signal source this lead is, to store with the lead: hiring-for-supported-roles (a company job post), tool-recommendation-asks (asks for a pick or an alternative), solution-complaints (only complains), community-questions (any other ask)"New value: +"Which buying-signal source this lead is, to store with the lead: hiring-for-supported-roles (a company job post), tool-recommendation-asks (asks for a pick or an alternative), solution-complaints (only complains), community-questions (any other ask), former-customers-moved (job_changes) or partnerships (partners)"
    • changedOutput schema / properties / results / items / properties / lead_source / enum
      Previous value: -[
      -  "tool-recommendation-asks",
      -  "solution-complaints",
      -  "hiring-for-supported-roles",
      -  "community-questions"
      -]New value: +[
      +  "tool-recommendation-asks",
      +  "solution-complaints",
      +  "hiring-for-supported-roles",
      +  "community-questions",
      +  "former-customers-moved",
      +  "partnerships"
      +]
    • changedOutput schema / properties / results / items / properties / quote / description
      Previous value: -"A quote of the ask, under 15 words"New value: +"A quote of the ask under 15 words; for job_changes the filer and the former customer it names, for partners the listing's own summary"
    • changedOutput schema / properties / results / items / properties / source / description
      Previous value: -"Where the post is: hackernews, hn_hiring (the monthly hiring thread), github or stackexchange"New value: +"Where the lead is: hackernews, hn_hiring (the monthly hiring thread), github, stackexchange, job_changes (an SEC 8-K) or partners (a WordPress.org listing)"
    • changedOutput schema / properties / results / items / properties / source / enum
      Previous value: -[
      -  "hackernews",
      -  "hn_hiring",
      -  "github",
      -  "stackexchange"
      -]New value: +[
      +  "hackernews",
      +  "hn_hiring",
      +  "github",
      +  "stackexchange",
      +  "job_changes",
      +  "partners"
      +]
    • changedOutput schema / properties / results / items / properties / url / description
      Previous value: -"Link to the post. For Stack Exchange this link is also the CC BY-SA attribution"New value: +"Link to the post, filing or listing. For Stack Exchange this link is also the CC BY-SA attribution"
  3. Changed6 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "lookback_days": 30,
      +    "service": "SEO audit"
      +  }
      +]
    • changedOutput schema / properties / as_of / description
      Previous value: -"Date of this answer (UTC, YYYY-MM-DD)"New value: +"ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch."
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / source
      Added value: +{
      +  "description": "Who the data comes from, to cite and to check it against.",
      +  "properties": {
      +    "name": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "url"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / untrusted_source
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "status",
      -  "service",
      -  "posts_read",
      -  "posts_about_service",
      -  "intent_count",
      -  "complaint_count",
      -  "sources_used",
      -  "sources_unavailable",
      -  "reddit",
      -  "attribution",
      -  "how_scored",
      -  "as_of",
      -  "notice",
      -  "window",
      -  "dropped",
      -  "results"
      -]New value: +[
      +  "status",
      +  "service",
      +  "posts_read",
      +  "posts_about_service",
      +  "intent_count",
      +  "complaint_count",
      +  "sources_used",
      +  "sources_unavailable",
      +  "reddit",
      +  "attribution",
      +  "how_scored",
      +  "as_of",
      +  "notice",
      +  "window",
      +  "dropped",
      +  "results",
      +  "untrusted_source",
      +  "note",
      +  "source"
      +]
  4. Added
  5. Removed
  6. Changed3 schema fields changed
    • changedInput schema / properties / keywords / description
      Previous value: -"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"New value: +"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"
    • addedOutput schema / properties / results / items / properties / reply_angle
      Added value: +{
      +  "description": "One line on what to reply. It never names the tool or the subject, so open the link to read it. Picked by rule from the strongest cue: thanks (check the thread first), a budget, a hire, a named friction, an alternative, a recommendation, or a complaint with no ask",
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "rank",
      -  "source",
      -  "url",
      -  "date",
      -  "quote",
      -  "intent_score",
      -  "label",
      -  "reason",
      -  "signals"
      -]New value: +[
      +  "rank",
      +  "source",
      +  "url",
      +  "date",
      +  "quote",
      +  "intent_score",
      +  "label",
      +  "reason",
      +  "signals",
      +  "reply_angle"
      +]
  7. Changed2 schema fields changed
    • addedInput schema / properties / sources
      Added value: +{
      +  "description": "Which public sources to read: hackernews (comments and Ask HN), github (open and closed issues) and stackexchange. Default is all three. Leave one out to skip it, for example stackexchange when it is rate limited",
      +  "items": {
      +    "enum": [
      +      "hackernews",
      +      "github",
      +      "stackexchange"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 3,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedOutput schema / properties / results / items / properties / source / enum
      Previous value: -[
      -  "hackernews",
      -  "stackexchange"
      -]New value: +[
      +  "hackernews",
      +  "github",
      +  "stackexchange"
      +]
  8. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: results come from plain rules with no AI model, are leads rather than sure sales, exclude usernames and contact details, and do not search Reddit. It also explains the free-tier rate limit of 4 lookups per day per network, shared with weekly_brief, reset at 00:00 UTC, and that repeats within 6 hours come from cache and count nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the primary use case and is dense with useful operational details. It is somewhat long and includes some parameter repetition already covered by the schema, but no sentence is clearly wasted and the overall flow is coherent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has annotations, an output schema, and 100% schema description coverage, the description supplies the remaining context an agent needs: return sources, output fields, caveats, sibling alternatives, and rate limits. Nothing essential for correct invocation appears to be missing.

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%, so the schema already documents parameter meanings, defaults, ranges, and examples thoroughly. The description repeats key parameter facts such as service examples, lookback_days range, and limit defaults, but adds no meaningful semantics beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: finding public posts where people ask for a service the user sells, with concrete examples. It clearly distinguishes the tool from siblings such as weekly_brief and find_buyer_signals, so an agent can identify its role without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance and names alternatives with conditions: use it instead of weekly_brief for non-7-day lookbacks or a set limit, and use find_buyer_signals for funded companies. It also states it is not for finding who wrote a post, and includes clear exclusions such as Reddit not being searched.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.