search_signals
Semantic search over the full EchoSift pain signal corpus. Pass the build context or idea in natural language and get back the real developer pains that match.
Use this as the entry point for a build/validate decision. Follow up with get_pain_signal and get_signal_evidence to go deeper.
Parameters
Section titled “Parameters”| Name | Type | Required | Description |
|---|---|---|---|
q |
string | yes | Natural-language search query (3-500 chars) |
limit |
integer | no | Max results to return (1-50, default 20) |
Example call
Section titled “Example call”{ "name": "search_signals", "arguments": { "q": "webhook delivery reliability retries", "limit": 10 }}Truncated response shape
Section titled “Truncated response shape”Search: "webhook delivery reliability retries"10 results
1. Webhook delivery failure and retry handling score=87.2 volume=1840 growth=+1.2x owners=34 id: 3f9a1c2d-...
2. HTTP callback timeouts in CI pipelines score=71.0 volume=690 growth=+0.6x owners=12 id: a2b8f3e1-...
...Scope note
Section titled “Scope note”EchoSift covers pain evidence and market breadth (how many companies feel a pain). It does not cover pricing, market size in dollars, or competitor product analysis. Say so rather than inventing them.