Creates dataEngagements (vendor pipeline)MCP tool

`engagements_create`

Create a new vendor engagement to track a meeting, call, or event with a vendor.

Create a new vendor engagement to track a meeting, call, or event with a vendor. WORKFLOW: 1) Optionally use contacts_list to find the contact and prospects_list to find the prospect 2) Create the engagement with vendor_type, type, and schedule details. Returns the created engagement with ID and display_id.

Parameters#

Parameter	Type	Required	Description
`contact_id`	string	No	UUID of an existing contact for this engagement. Use `contacts_list` to find. · Format: UUID
`vendor_type`	string	Yes	Type of vendor (e.g. lender, inspector, escrow_officer, title_rep, appraiser, contractor, photographer)
`prospect_id`	string	No	UUID of the linked prospect. Use `prospects_list` to find. · Format: UUID
`title`	string	No	Title or description for this engagement (e.g. "Coffee with John - Title Rep")
`engagement_type`	string	No	Type of engagement (e.g. coffee_meeting, lunch, phone_call, office_visit, networking_event, training, co_marketing)
`scheduled_date`	string	No	Date of the engagement (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD)
`scheduled_time`	string	No	Time of the engagement (e.g. "14:30", "2:30 PM")
`duration_minutes`	number	No	Expected duration in minutes (e.g. 30, 60, 90) · Min: 1
`location`	string	No	Physical location or address for the engagement
`meeting_url`	string	No	Virtual meeting URL (Zoom, Google Meet, etc.)
`notes`	string	No	Additional notes or agenda items for the engagement
`tags`	array of strings	No	Tags for categorization (e.g. ["first-meeting", "follow-up", "co-marketing"])

Example prompts#

"Set up a coffee meeting with lender Marcus Hale next Tuesday at 9 at Brew House."
"Schedule a 60 minute Zoom training with the inspector team Friday at 2."

Safety#

Creates data. Creates a new record in your CRM and may trigger notifications or webhooks. Running it twice creates a duplicate, so Claude runs it once per request.