Updates dataEngagements (vendor pipeline)MCP tool
engagements_update
Update an existing vendor engagement's information or status.
Update an existing vendor engagement's information or status. Only provided fields are updated - omitted fields remain unchanged. Common uses: status change (proposed->scheduled->in_progress->completed), reschedule, add follow-up notes. Returns the updated engagement record.Parameters#
| Parameter | Type | Required | Description |
|---|---|---|---|
engagement_id | string | Yes | UUID of the engagement to update (required). Use engagements_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 |
prospect_id | string | No | Updated prospect ID. Use prospects_list to find. · Format: UUID |
title | string | No | Updated title |
engagement_type | string | No | Updated engagement type |
status | enum | No | Updated status · One of: proposed, scheduled, in_progress, follow_up, completed, cancelled |
scheduled_date | string | No | Updated scheduled date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) |
scheduled_time | string | No | Updated scheduled time |
duration_minutes | number | No | Updated duration in minutes · Min: 1 |
location | string | No | Updated location |
meeting_url | string | No | Updated meeting URL |
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 care_status_updated_at and care_status_updated_by audit columns. · One of: no_status, cared, needs_care, didnt_care |
care_status_note | string | No | Note explaining the care status change (audit trail). |
completed_at | string | No | Timestamp the engagement was completed. Usually set alongside status=completed. (ISO 8601 format, e.g., 2025-01-22T14:30:00Z) · Format: Date-time (ISO 8601) |
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#
- "Push my lunch with the title rep to next Wednesday at noon."
- "Mark Tuesday's coffee with Marcus Hale completed and note he wants co-marketing flyers."
Safety#
Updates data. Changes an existing record. The change is visible immediately in the app and can be edited back.