get_signal_timeline

Returns two time series for a pain signal in one call:

1. Daily mention timeline: how many developer posts mentioned this pain per day. Useful for distinguishing a spike from a sustained trend.
2. Tracked history: how the signal’s owner count, score, and volume evolved over time (from nightly snapshots).

Use this before writing an opportunity brief to confirm that growth is real and not a one-day anomaly.

Parameters

Name	Type	Required	Description
id	string (UUID)	yes	Pain signal UUID
timelineDays	integer	no	Days of daily mention buckets (1-365, default: 30)
historyDays	integer	no	Days of owner/score/volume history (1-365, default: 90)

Example call

{
  "name": "get_signal_timeline",
  "arguments": {
    "id": "3f9a1c2d-8b4e-4f1a-9c2d-1e5a3b7f9c2e",
    "timelineDays": 30,
    "historyDays": 90
  }
}

Response shape

Timeline section

Daily mentions (last 30 days):
  2026-07-01: 42
  2026-07-02: 38
  2026-07-03: 61
  ...
  totalMentions: 1240

History section

Tracked history (90 days):
  2026-04-19: ownerCount=8  score=62.1  volume=740
  2026-04-26: ownerCount=11 score=68.4  volume=890
  ...
  trackingStartedAt: 2026-04-19

Days with zero mentions are omitted from the timeline; the history points are the nightly snapshot cadence (typically daily).

Interpretation tips

• A single spike followed by flat activity is usually a viral post, not a sustained market pain.
• Owner count growing steadily over weeks is a stronger signal than a score spike.
• trackingStartedAt being recent means the signal is new; treat it with more uncertainty.