Creates dataComposite workflowsMCP tool
log_showing_with_feedback
Log a property showing AND capture client feedback in ONE call.
Log a property showing AND capture client feedback in ONE call. Use after showing a property to a buyer client. Creates a completed appointment record, logs the showing activity, and records feedback (interest level, pros, cons, notes). Equivalent to: appointments_create → appointments_update (status=completed) → log_call (with feedback notes). Returns the showing record with feedback. Use listings_list first to get listing_id if unknown.
Parameters#
| Parameter | Type | Required | Description |
|---|---|---|---|
client_id | string | Yes | UUID of the buyer client being shown the property. Use clients_list to find. · Format: UUID |
listing_id | string | No | UUID of the listing being shown. Use listings_list to find by address. · Format: UUID |
property_address | string | No | Property address (required if no listing_id — for unlisted properties) |
showing_time | string | No | When the showing occurred (defaults to now). ISO 8601 format, e.g., 2025-01-22T14:30:00Z. · Format: Date-time (ISO 8601) |
duration_minutes | number | No | Duration in minutes (default: 30) · Max: 480 · Min: 5 |
interest_level | enum | Yes | Client interest level after viewing (required) · One of: very_interested, interested, neutral, not_interested, rejected |
would_offer | boolean | No | Would the client consider making an offer on this property? |
pros | array of strings | No | What the client liked (e.g., ["big backyard", "updated kitchen", "quiet street"]) |
cons | array of strings | No | What the client disliked (e.g., ["small bedrooms", "needs roof work", "busy road"]) |
feedback_notes | string | No | Detailed feedback or notes from the showing |
schedule_follow_up | boolean | No | If true, schedules a follow-up call for next business day |
Example prompts#
- "Log the showing at 67 Maple Ct, the Garcias loved the yard but hated the kitchen."
- "Record that Marcus toured 230 Sandpiper Way, very interested, and wants to write an offer."
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.