Updates dataProspects (vendor pipeline)MCP tool
prospects_update
Update an existing vendor prospect's information or status.
Update an existing vendor prospect's information or status. Only provided fields are updated - omitted fields remain unchanged. Common uses: status change (identified->researching->outreach->responded->nurturing->converted), update interest level, add notes. Returns the updated prospect record.Parameters#
| Parameter | Type | Required | Description |
|---|---|---|---|
prospect_id | string | Yes | UUID of the prospect to update (required). Use prospects_list to find. · Format: UUID |
contact_id | string | No | Updated contact ID. Use contacts_list to find. · Format: UUID |
vendor_type | string | No | Updated vendor type |
title | string | No | Updated title |
source | string | No | Updated source |
status | enum | No | Updated status · One of: identified, researching, outreach, responded, nurturing, converted, disqualified, lost |
interest_level | enum | No | Updated interest level · One of: cold, warm, hot |
priority | enum | No | Updated priority · One of: low, medium, high, urgent |
estimated_ltv | number | No | Updated estimated lifetime value · Min: 0 |
notes | string | No | Updated notes |
tags | array of strings | No | Updated tags array (replaces existing tags) |
care_status | enum | No | Care status for tracking. Setting this also updates the audit columns. · One of: no_status, cared, needs_care, didnt_care |
care_status_note | string | No | Note explaining the care status change. |
record_data | object (free-form) | No | Pipeline-specific vertical data as a JSON object. Replaces (does not merge with) the existing record_data. |
Example prompts#
- "Mark the Rosa Delgado prospect as responded and bump her to high priority."
- "Move my Summit Lending prospect to nurturing and note our coffee meeting Tuesday."
Safety#
Updates data. Changes an existing record. The change is visible immediately in the app and can be edited back.