update_lead
Change fields on one existing lead: notes, assignee, contact details or pipeline stage. Only the keys supplied are written; the rest of the record is left as it is. A key that is not writable is refused with the list of fields that are, so a misspelled field cannot pass as a successful write.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"lead_id": "<lead_id>",
"fields": "<fields>"
},
"name": "update_lead"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fields | Yes | Object of field name to new value, for example {"stage": "qualified", "notes": "Called back"}. Fields not listed keep their current value. Writable fields: assigned_to, company_name, contact_email, contact_name, contact_phone, estimated_monthly_budget, estimated_monthly_fee, expected_close_date, last_contact_at, lost_reason, notes, probability_pct, proposal_id, source, stage, tags, website. | |
| lead_id | Yes | ADS Beast id of the lead to change. |