Signals & Scoring
Understand lead scoring — view score breakdowns, signal history, and campaign weight configuration.
Tools (4)
Section titled “Tools (4)”get_lead_score_breakdown
Section titled “get_lead_score_breakdown”Full name: campaignstack_get_lead_score_breakdown
Get a detailed breakdown of a lead’s score in a campaign. Shows ICP score, individual signal contributions with all multipliers (time decay, recency bonus, intent, topic alignment, connection degree), and the total computed score. Call this when the user asks why a lead scored high or low. It does not list signal detail, use campaignstack_list_lead_signals for that, or change scoring, use campaignstack_update_campaign_weight for that.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
campaignId | string | Yes | — | (min length: 1) |
leadSource | global | private | No | "global" | |
leadId | string | Yes | — | (min length: 1) |
list_lead_signals
Section titled “list_lead_signals”Full name: campaignstack_list_lead_signals
List recent signals detected for a lead: job changes, engagement activity, and similar events. Signals are profile changes or engagement events that affect scoring. Sorted by detection time, newest first. Call this when the user asks what changed about a lead or why it moved in score recently. It lists the events only; for the scoring math itself use campaignstack_get_lead_score_breakdown.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
leadSource | global | private | No | "global" | |
leadId | string | Yes | — | (min length: 1) |
limit | integer | No | 20 | (min: 1, max: 50) |
cursor | number | No | — |
get_campaign_weights
Section titled “get_campaign_weights”Full name: campaignstack_get_campaign_weights
Get signal weight configuration for a campaign. Shows all signal types with their score impact, whether they’re enabled, and whether the weight is custom or default. Call this before tuning scoring, so current weights can be read back to the user. It only reads the configuration; campaignstack_update_campaign_weight changes it.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
campaignId | string | Yes | — | (min length: 1) |
update_campaign_weight
Section titled “update_campaign_weight”Full name: campaignstack_update_campaign_weight
Update the weight (score impact) of a signal type for a campaign. Call this when the user names a signal type and a new score impact; read current weights first with campaignstack_get_campaign_weights. This changes future scoring only, not existing lead scores.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
campaignId | string | Yes | — | (min length: 1) |
signalType | string | Yes | — | (min length: 1) |
scoreImpact | number | Yes | — | (min: -100, max: 100) |