trending_signals

Returns what is happening now in developer pain. Use for morning briefings, idea hunting, and spotting opportunities before they are obvious.

Three modes:

• trending: highest recent growth regardless of volume.
• emerging: low-volume, high-growth signals. Early signals before they become crowded.
• top: best signals by a chosen metric.

Parameters

Name	Type	Required	Description
mode	enum	yes	trending, emerging, or top
metric	enum	no	For mode=top only: score, growth, or volume (default: score)
limit	integer	no	Number of results (1-20, default: 10)
maxVolume	integer	no	For mode=emerging: max volume threshold (default: 100)
minGrowth	number	no	For mode=emerging: min growth rate (default: 0.5)

Example call: morning briefing

{
  "name": "trending_signals",
  "arguments": {
    "mode": "trending",
    "limit": 10
  }
}

Example call: early opportunities

{
  "name": "trending_signals",
  "arguments": {
    "mode": "emerging",
    "maxVolume": 80,
    "minGrowth": 1.0,
    "limit": 8
  }
}

Truncated response shape

Trending signals (mode=trending, 10 results)

1. LLM function-calling schema validation errors
   score=88.1  volume=2140  growth=+3.4x  owners=29
   id: 4a7d1e8c-...

2. Token budget exhaustion in long-context reasoning
   score=82.5  volume=1780  growth=+2.8x  owners=22
   id: 9f3b2c1a-...

...

Tips

• Use mode=emerging + minGrowth=1.5 to find pains that doubled in the last window.
• Follow up with get_pain_signal to inspect owners and brief before making any build call.