# ActuallyCare Docs — MCP tool reference # MCP tool reference > Every public tool the ActuallyCare MCP server exposes to Claude — 242 tools across 41 categories. The ActuallyCare MCP server has **242 tools** across **41 categories** — everything from looking up an escrow to drafting a review request. This reference documents every one of them. You don't need to memorize tool names. Just ask Claude in plain English — it picks the right tool. To keep conversations fast, Claude's apps (claude.ai, Desktop, and Claude Code) get a set of everyday tools, and Claude can only use those. If a tool here isn't in Claude's tool list, Claude can't use it yet. [Custom apps](/mcp/custom-apps) can call any tool by name. A note on wording: each tool's description below is the **literal instruction text Claude reads** when deciding how to use the tool. Some of it is written *to Claude* ("Do NOT ask for missing fields…") rather than to you — we publish it verbatim so you can see exactly what Claude is told. Machine-readable index: [`tools.json`](/tools.json) --- # Agent brokerage history > Look up which brokerage an agent was at on a given date, from California DRE public records. Look up which brokerage an agent was at on a given date, from California DRE public records. ## Tools (2) | Tool | Type | What it does | | --- | --- | --- | | [`agent_brokerage_at_date`](/tools/agent-brokerage-history/agent_brokerage_at_date) | Read-only | Resolve which brokerage an agent was at on a specific date. | | [`agent_brokerage_history_list`](/tools/agent-brokerage-history/agent_brokerage_history_list) | Read-only | List the full brokerage career timeline for an agent. | --- # agent_brokerage_at_date > Resolve which brokerage an agent was at on a specific date. Resolve which brokerage an agent was at on a specific date. Returns the brokerage name, DRE license number, and date range of the matching responsible-broker relationship from CA DRE public records. Use this when a user asks "which brokerage was X at on Y date" or for historical escrow attribution. Returns null when the date predates the agent's recorded history (DRE typically goes back ~5–10 years). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `user_id` | string | No | Platform user UUID. Defaults to the calling user when omitted. | | `dre_license_id` | string | No | CA DRE 8-digit license number (alternative to user_id, useful for non-platform agents on a listing). | | `on_date` | string | Yes | Date to resolve, in YYYY-MM-DD format. Both period start_date and end_date are inclusive bounds. · Format: Date (YYYY-MM-DD) | ## Example prompts - "Which brokerage was I working under on March 15, 2022?" - "Which brokerage was the agent with DRE license 01987654 at on June 15, 2019?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # agent_brokerage_history_list > List the full brokerage career timeline for an agent. List the full brokerage career timeline for an agent. Use to answer where an agent has worked and for how long — for a point-in-time lookup, use [`agent_brokerage_at_date`](/tools/agent-brokerage-history/agent_brokerage_at_date) instead. Returns one entry per (brokerage, period) tuple, oldest first, including current responsible broker (end_date is null for current). Each entry includes brokerage name, DRE license, start/end dates, and a human-readable tenure label like "1 year, 7 months". Sourced from CA DRE public records. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `user_id` | string | No | Platform user UUID. Defaults to the calling user when omitted. | | `dre_license_id` | string | No | CA DRE 8-digit license number (alternative to user_id, useful for non-platform agents on a listing). | ## Example prompts - "Show me my full brokerage career timeline with tenure at each office." - "Pull the brokerage history for the listing agent with DRE license 02114478." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Agent Reports > Tools for agent reports. Tools for agent reports. ## Tools (3) | Tool | Type | What it does | | --- | --- | --- | | [`agent_reports_publish`](/tools/agent-reports/agent_reports_publish) | Creates data | Store a scheduled-routine report (daily plan, daily review, or weekly plan) about the ActuallyCare PLATFORM CODEBASE. | | [`agent_reports_list`](/tools/agent-reports/agent_reports_list) | Read-only | List recent scheduled-routine reports about the ActuallyCare PLATFORM CODEBASE, newest first. | | [`agent_reports_get`](/tools/agent-reports/agent_reports_get) | Read-only | Fetch one scheduled-routine report about the ActuallyCare PLATFORM CODEBASE in full, including its markdown body. | --- # agent_reports_get > Fetch one scheduled-routine report about the ActuallyCare PLATFORM CODEBASE in full, including its markdown body. Fetch one scheduled-routine report about the ActuallyCare PLATFORM CODEBASE in full, including its markdown body. Identify it either by id, or by the (report_type, report_date) pair. Use this after [`agent_reports_list`](/tools/agent-reports/agent_reports_list) when you need the detail of one specific prior report. Platform-engineering tooling. Not related to CRM data. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | No | The report id. Takes precedence over report_type + report_date if both are given. | | `report_type` | enum | No | Used with report_date to identify the report. · One of: `daily_plan`, `daily_review`, `weekly_plan` | | `report_date` | string | No | Used with report_type to identify the report (YYYY-MM-DD). · Format: Date (YYYY-MM-DD) | ## Example prompts - "Pull up the details on one of my agent reports." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # agent_reports_list > List recent scheduled-routine reports about the ActuallyCare PLATFORM CODEBASE, newest first. List recent scheduled-routine reports about the ActuallyCare PLATFORM CODEBASE, newest first. Call this at the START of a routine run to see what previous runs concluded — what was planned yesterday, what shipped, what was flagged as needing attention and whether it was resolved. Returns titles, summaries and needs_attention items. It deliberately does NOT return full report bodies; use [`agent_reports_get`](/tools/agent-reports/agent_reports_get) for one specific report when you need the detail. Platform-engineering tooling. Not related to CRM data. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `report_type` | enum | No | Only return reports of this type. Omit for all types. · One of: `daily_plan`, `daily_review`, `weekly_plan` | | `limit` | integer | No | How many reports to return, newest first. Default 7. · Default: `7` · Max: 30 · Min: 1 | ## Example prompts - "Show me my agent reports." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # agent_reports_publish > Store a scheduled-routine report (daily plan, daily review, or weekly plan) about the ActuallyCare PLATFORM CODEBASE. Store a scheduled-routine report (daily plan, daily review, or weekly plan) about the ActuallyCare PLATFORM CODEBASE. This is platform-engineering tooling for automated routines. It has nothing to do with escrows, clients, leads, or any CRM record — never call it to answer a question about real estate data. Publishing is idempotent on (report_type, report_date): re-publishing the same type and date CORRECTS the existing report rather than creating a second one. That is deliberate — these routines re-arm themselves on retry. Pass the report body as markdown. It is rendered to HTML for email and web at read time, so do not send HTML. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `report_type` | enum | Yes | Which routine produced this report. · One of: `daily_plan`, `daily_review`, `weekly_plan` | | `report_date` | string | Yes | The day the report COVERS (YYYY-MM-DD), not the time it ran. Half of the idempotency key. · Format: Date (YYYY-MM-DD) | | `title` | string | Yes | Subject-line-worthy title, e.g. "2026-08-08 — daily review". · Max length: 500 · Min length: 1 | | `summary_md` | string | No | One or two sentences. Used as the email preheader and the calendar event description. · Max length: 2000 | | `body_md` | string | Yes | The full report as markdown. Do NOT send HTML. · Min length: 1 | | `needs_attention` | array of objects | No | Structured list of items requiring a human. Empty array means nothing is blocked. · Max items: 10 | | `needs_attention[].title` | string | Yes | Max length: 300 | | `needs_attention[].detail` | string | No | Max length: 1000 | | `needs_attention[].urgency` | enum | No | One of: `low`, `medium`, `high` | | `facts` | object | No | Machine-readable findings — commit counts, PR numbers, queue depth. Free-form. | | `generated_at` | string | No | ISO-8601 timestamp of when the ANALYSIS was performed. Defaults to now. A publish carrying an older generated_at than the stored report is dropped, so a late retry cannot overwrite a newer report. | | `routine_id` | string | No | The scheduling trigger id (trig_...) that produced this, for provenance. · Max length: 100 | | `git_sha_range` | string | No | Commit range the report covers, e.g. "abc1234..def5678". · Max length: 100 | ## Example prompts - "Store a scheduled-routine report (daily plan, daily review, or weekly plan) about the ActuallyCare PLATFORM CODEBASE — just ask in plain English." ## 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. --- # Appointments > Create, search, update, and cancel appointments — including today's schedule and appointment stats. Create, search, update, and cancel appointments — including today's schedule and appointment stats. ## Tools (10) | Tool | Type | What it does | | --- | --- | --- | | [`appointments_create`](/tools/appointments/appointments_create) | Creates data | Create a new appointment, showing, meeting, or follow-up. | | [`appointments_list`](/tools/appointments/appointments_list) | Read-only | Search for appointments by date range, status, or text. | | [`appointments_get`](/tools/appointments/appointments_get) | Read-only | Get full details of a specific appointment by its ID — time, location, type, status, and notes. | | [`appointments_update`](/tools/appointments/appointments_update) | Updates data | Update an existing appointment's details or reschedule it. | | [`appointments_cancel`](/tools/appointments/appointments_cancel) | Irreversible | Cancel an appointment while keeping its record for history. | | [`appointments_today`](/tools/appointments/appointments_today) | Read-only | Get all appointments scheduled for today. | | [`appointments_archive`](/tools/appointments/appointments_archive) | Updates data | Archive an appointment to hide it from active views without deleting it. | | [`appointments_restore`](/tools/appointments/appointments_restore) | Updates data | Restore a previously archived appointment back to active views. | | [`appointments_delete`](/tools/appointments/appointments_delete) | Irreversible | Permanently delete an appointment. | | [`appointments_stats`](/tools/appointments/appointments_stats) | Read-only | Get aggregate statistics for all appointments: counts by status (scheduled/completed/cancelled), upcoming appointments within 7 days, and total counts by type. | --- # appointments_archive > Archive an appointment to hide it from active views without deleting it. Archive an appointment to hide it from active views without deleting it. Archived appointments can be restored later with [`appointments_restore`](/tools/appointments/appointments_restore). Use this for past appointments you want to declutter from your schedule view. Returns the archived appointment record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `appointment_id` | string | Yes | UUID of the appointment to archive. Use [`appointments_list`](/tools/appointments/appointments_list) to find the ID if unknown. | ## Example prompts - "Archive that old showing from last month so it stops cluttering my schedule." - "Hide the cancelled Patterson consultation from my active calendar without deleting it." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # appointments_cancel > Cancel an appointment while keeping its record for history. Cancel an appointment while keeping its record for history. Use when a showing, meeting, or follow-up is called off; to move it to a new time instead, use [`appointments_update`](/tools/appointments/appointments_update). Returns the cancelled appointment record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `appointment_id` | string | Yes | UUID of the appointment to cancel · Format: UUID | | `reason` | string | No | Reason for cancellation | ## Example prompts - "Cancel my 4pm property tour with the Nguyens, they got stuck at work." - "Cancel Thursday's appraisal at 412 Birchwood Ln, but double-check with me before you do it." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. ## Previous name This tool was previously published as `cancel_appointment`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # appointments_create > Create a new appointment, showing, meeting, or follow-up. Create a new appointment, showing, meeting, or follow-up. Use whenever the user wants something on their calendar. Call immediately with whatever data the user provides. Do NOT ask for missing fields — the system shows an editable draft card where the user can fill in remaining details. Returns the created appointment record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `title` | string | Yes | Title or subject of the appointment | | `appointment_type` | enum | No | Type of appointment · One of: `buyer_consultation`, `lender_prequalification`, `listing_appointment`, `showing`, `property_tour`, `client_meeting`, `inspection`, `appraisal`, `signing`, `final_walkthrough`, `call`, `other`, `open_house`, `escrow_deadline`, `owner_blackout`, `escrow_service` | | `start_time` | string | Yes | Start date and time (ISO 8601 format, e.g., 2025-01-15T14:00:00) | | `end_time` | string | No | End date and time (ISO 8601 format) | | `location` | string | No | Location or address of the appointment | | `notes` | string | No | Notes or description | | `contact_id` | string | No | UUID of the contact this appointment is with | | `listing_id` | string | No | UUID of the listing this appointment is for (if applicable) | ## Example prompts - "Schedule a buyer consultation with the Garcias tomorrow at 2pm at my office." - "Book a listing appointment at 412 Birchwood Ln on Friday at 10am." ## 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. ## Previous name This tool was previously published as `create_appointment`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # appointments_delete > Permanently delete an appointment. Permanently delete an appointment. This is IRREVERSIBLE - the appointment will be hidden from all views including archived. Only use for test data or duplicate records. For normal cleanup, use [`appointments_archive`](/tools/appointments/appointments_archive) instead which is reversible. Returns confirmation of the deletion. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `appointment_id` | string | Yes | UUID of the appointment to delete. Use [`appointments_get`](/tools/appointments/appointments_get) first to verify. | ## Example prompts - "Permanently delete the duplicate signing appointment I accidentally created twice." - "Delete that test appointment for good, but confirm with me before it's gone forever." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # appointments_get > Get full details of a specific appointment by its ID — time, location, type, status, and notes. Get full details of a specific appointment by its ID — time, location, type, status, and notes. Use after [`appointments_list`](/tools/appointments/appointments_list) when you need every field for one appointment. For multiple appointments, pass appointment_ids instead. Returns the complete appointment record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `appointment_id` | string | No | UUID of a single appointment to retrieve · Format: UUID | | `appointment_ids` | array of strings | No | Array of appointment UUIDs for batch retrieval (max 100). Use either appointment_id OR appointment_ids, not both. · Max items: 100 | ## Example prompts - "Pull up the full details for my 3pm signing appointment." - "What are the notes and location on the Hendersons buyer consultation?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `get_appointment`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # appointments_list > Search for appointments by date range, status, or text. Search for appointments by date range, status, or text. Use to answer calendar questions or to find an appointment's ID before updating or cancelling it (for today's schedule, [`appointments_today`](/tools/appointments/appointments_today) is faster). Returns IDs only by default for efficiency; use the fields parameter to include additional data. Response includes relatedIds.contactIds for chainable operations. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term — matches against title and location (case-insensitive partial match) | | `start_date` | string | No | Start date to filter from (YYYY-MM-DD) | | `end_date` | string | No | End date to filter to (YYYY-MM-DD) | | `appointment_type` | enum | No | Filter by appointment type · One of: `buyer_consultation`, `lender_prequalification`, `listing_appointment`, `showing`, `property_tour`, `client_meeting`, `inspection`, `appraisal`, `signing`, `final_walkthrough`, `call`, `other`, `open_house`, `escrow_deadline`, `owner_blackout`, `escrow_service` | | `status` | enum | No | Filter by appointment status · One of: `scheduled`, `completed`, `cancelled`, `no_show` | | `fields` | array of enum | No | Field groups to include. Empty/omitted = IDs only. Options: basic (id, title, type, status), schedule (times, location), contacts (contact name), full (all fields). · Values: `basic`, `schedule`, `contacts`, `full` | | `limit` | string | No | Max results. Use a number (e.g. "25") or "all". Default: 10. "all" and any value above 200 are capped at 200 server-side. | ## Example prompts - "What showings do I have on the calendar next week?" - "Find all my scheduled inspections between June 15 and June 30." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `list_appointments`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # appointments_restore > Restore a previously archived appointment back to active views. Restore a previously archived appointment back to active views. Reverses the effect of [`appointments_archive`](/tools/appointments/appointments_archive). Use this when an appointment was archived by mistake. Returns the restored appointment record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `appointment_id` | string | Yes | UUID of the appointment to restore. Must be currently archived. | ## Example prompts - "Restore the Lopez walkthrough I archived by mistake yesterday." - "Bring back that archived inspection appointment for 67 Maple Ct." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # appointments_stats > Get aggregate statistics for all appointments: counts by status (scheduled/completed/cancelled), upcoming appointments within 7 days, and total counts by type. Get aggregate statistics for all appointments: counts by status (scheduled/completed/cancelled), upcoming appointments within 7 days, and total counts by type. Use this for dashboard metrics and scheduling overview. Does NOT return individual appointment records - use [`appointments_list`](/tools/appointments/appointments_list) for that. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "How many appointments do I have coming up in the next seven days?" - "Give me a breakdown of my completed versus cancelled appointments this month." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # appointments_today > Get all appointments scheduled for today. Get all appointments scheduled for today. Use when user asks about today's schedule or calendar. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "What does my schedule look like today?" - "Run through everything on my calendar for today before I leave the house." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `get_today_schedule`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # appointments_update > Update an existing appointment's details or reschedule it. Update an existing appointment's details or reschedule it. Only provided fields are updated — omitted fields remain unchanged. Common uses: move the start/end time, change the location, or fix the title. Returns the updated appointment record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `appointment_id` | string | Yes | UUID of the appointment to update · Format: UUID | | `title` | string | No | Updated title | | `start_time` | string | No | Updated start time (ISO 8601) | | `end_time` | string | No | Updated end time (ISO 8601) | | `location` | string | No | Updated location | | `notes` | string | No | Updated notes | | `status` | enum | No | Updated status · One of: `scheduled`, `completed`, `cancelled`, `no_show` | ## Example prompts - "Move the Garcias showing from Saturday to Sunday at 1pm." - "Mark yesterday's listing appointment at 88 Calloway Dr as completed." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. ## Previous name This tool was previously published as `update_appointment`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # Bulk operations > Bulk archive, restore, and delete across core entities, plus bulk lead status updates. Bulk archive, restore, and delete across core entities, plus bulk lead status updates. ## Tools (19) | Tool | Type | What it does | | --- | --- | --- | | [`bulk_update_lead_status`](/tools/bulk-operations/bulk_update_lead_status) | Bulk changes | Update multiple leads' status at once for bulk lead management. | | [`contacts_batch_archive`](/tools/bulk-operations/contacts_batch_archive) | Bulk changes | Archive multiple contacts at once. | | [`contacts_batch_restore`](/tools/bulk-operations/contacts_batch_restore) | Bulk changes | Restore multiple archived contacts at once. | | [`contacts_batch_delete`](/tools/bulk-operations/contacts_batch_delete) | Bulk changes | Permanently delete multiple contacts that have been archived. | | [`leads_batch_archive`](/tools/bulk-operations/leads_batch_archive) | Bulk changes | Archive multiple leads at once. | | [`leads_batch_restore`](/tools/bulk-operations/leads_batch_restore) | Bulk changes | Restore multiple archived leads at once. | | [`leads_batch_delete`](/tools/bulk-operations/leads_batch_delete) | Bulk changes | Permanently delete multiple leads that have been archived. | | [`clients_batch_archive`](/tools/bulk-operations/clients_batch_archive) | Bulk changes | Archive multiple clients at once. | | [`clients_batch_restore`](/tools/bulk-operations/clients_batch_restore) | Bulk changes | Restore multiple archived clients at once. | | [`clients_batch_delete`](/tools/bulk-operations/clients_batch_delete) | Bulk changes | Permanently delete multiple clients that have been archived. | | [`escrows_batch_archive`](/tools/bulk-operations/escrows_batch_archive) | Bulk changes | Archive multiple escrows at once. | | [`escrows_batch_restore`](/tools/bulk-operations/escrows_batch_restore) | Bulk changes | Restore multiple archived escrows at once. | | [`escrows_batch_delete`](/tools/bulk-operations/escrows_batch_delete) | Bulk changes | Permanently delete multiple escrows that have been archived. | | [`appointments_batch_archive`](/tools/bulk-operations/appointments_batch_archive) | Bulk changes | Archive multiple appointments at once. | | [`appointments_batch_restore`](/tools/bulk-operations/appointments_batch_restore) | Bulk changes | Restore multiple archived appointments at once. | | [`appointments_batch_delete`](/tools/bulk-operations/appointments_batch_delete) | Bulk changes | Permanently delete multiple appointments that have been archived. | | [`listings_batch_archive`](/tools/bulk-operations/listings_batch_archive) | Bulk changes | Archive multiple listings at once. | | [`listings_batch_restore`](/tools/bulk-operations/listings_batch_restore) | Bulk changes | Restore multiple archived listings at once. | | [`listings_batch_delete`](/tools/bulk-operations/listings_batch_delete) | Bulk changes | Permanently delete multiple listings that have been archived. | --- # appointments_batch_archive > Archive multiple appointments at once. Archive multiple appointments at once. Sets appointment status to "cancelled" and marks them as soft-deleted. Returns success and failure counts with IDs. Use [`appointments_list`](/tools/appointments/appointments_list) first to verify the correct appointment IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Appointment UUIDs to archive. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Archive all my completed showings from last quarter in one sweep." - "Archive those 12 old appointments, but run the list past me before you do." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # appointments_batch_delete > Permanently delete multiple appointments that have been archived. Permanently delete multiple appointments that have been archived. Appointments must be archived before deletion. This action is irreversible. Returns success and failure counts with IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Appointment UUIDs to permanently delete. Must be archived. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Permanently delete the archived duplicate appointments from the calendar sync glitch." - "Purge those archived test appointments, but double-check with me before deleting them for good." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # appointments_batch_restore > Restore multiple archived appointments at once. Restore multiple archived appointments at once. Resets appointment status back to "scheduled" and clears the soft-delete timestamp. Returns success and failure counts with IDs. Restored appointments become active again. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Appointment UUIDs to restore. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Restore the batch of appointments that got archived during the calendar cleanup." - "Unarchive those five meetings from last week, but confirm which ones with me first." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # bulk_update_lead_status > Update multiple leads' status at once for bulk lead management. Update multiple leads' status at once for bulk lead management. > [!WARNING] > This affects multiple records permanently. Common use cases: marking old leads as "lost" after cleanup review, updating all contacted leads to "qualified" after qualification calls, batch setting leads to "unqualified" after failed contact attempts. Returns: count of successfully updated leads, any failures with reasons. Always verify the lead_ids list before calling — consider using [`leads_list`](/tools/leads/leads_list) first to confirm you have the right records. Status transitions: new→contacted→qualified→converted (success path) or →unqualified/lost (failure path). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `lead_ids` | array of strings | Yes | Array of lead UUIDs to update. Max 500 per call. Use [`leads_list`](/tools/leads/leads_list) to get IDs. · Max items: 500 · Min items: 1 | | `new_status` | enum | Yes | New status to set for ALL specified leads. converted should only be used via [`leads_convert`](/tools/leads/leads_convert) for proper client creation. · One of: `new`, `contacted`, `qualified`, `unqualified`, `converted`, `lost` | | `notes` | string | No | Notes to append to all updated leads. Example: "Bulk marked lost - no response after 6 months". · Max length: 1000 | ## Example prompts - "Mark all the leads I called yesterday as contacted in one go." - "Set those 30 stale Zillow leads to lost, but show me the list before updating." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # clients_batch_archive > Archive multiple clients at once. Archive multiple clients at once. Clients must be active (not already archived). Returns success and failure counts with IDs. Use [`clients_list`](/tools/clients/clients_list) first to verify the correct client IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Client UUIDs to archive. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Archive all the clients whose deals closed back in 2023 to tidy my dashboard." - "Archive these six expired buyer clients, but let me review the names first." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # clients_batch_delete > Permanently delete multiple clients that have been archived. Permanently delete multiple clients that have been archived. Clients must be archived before deletion. This action is irreversible. Returns success and failure counts with IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Client UUIDs to permanently delete. Must be archived. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Permanently delete the archived duplicate client records from the double import." - "Delete those archived test clients for good, but double-check with me before removing anything." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # clients_batch_restore > Restore multiple archived clients at once. Restore multiple archived clients at once. Clients must be currently archived. Returns success and failure counts with IDs. Restored clients become active again. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Client UUIDs to restore. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Restore the archived clients from the Henderson referral group, they're back in the market." - "Unarchive those three past clients, but confirm exactly who before you restore them." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # contacts_batch_archive > Archive multiple contacts at once. Archive multiple contacts at once. Contacts must be active (not already archived). Returns success and failure counts with IDs. Use [`contacts_list`](/tools/contacts/contacts_list) first to verify the correct contact IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Contact UUIDs to archive. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Archive all the vendor contacts from that lender event I never followed up with." - "Archive these 15 outdated contacts, but run the list by me before you do." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # contacts_batch_delete > Permanently delete multiple contacts that have been archived. Permanently delete multiple contacts that have been archived. Contacts must be archived before deletion. This action is irreversible. Returns success and failure counts with IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Contact UUIDs to permanently delete. Must be archived. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Permanently delete the duplicate contacts we archived after the CSV import mess." - "Wipe those 40 archived test contacts, but double-check with me before deleting anything." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # contacts_batch_restore > Restore multiple archived contacts at once. Restore multiple archived contacts at once. Contacts must be currently archived. Returns success and failure counts with IDs. Restored contacts become active again. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Contact UUIDs to restore. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Restore the batch of inspector contacts we archived during the spring cleanup." - "Bring back those 20 archived contacts, but confirm the list with me first." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # escrows_batch_archive > Archive multiple escrows at once. Archive multiple escrows at once. Escrows must be active (not already archived). Returns success and failure counts with IDs. Use [`escrows_list`](/tools/escrows/escrows_list) first to verify the correct escrow IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Escrow UUIDs to archive. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Archive all the escrows that closed before January to clean up my pipeline." - "Archive these four cancelled escrows, but show me the addresses before you do." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # escrows_batch_delete > Permanently delete multiple escrows that have been archived. Permanently delete multiple escrows that have been archived. Escrows must be archived before deletion. This action is irreversible. Returns success and failure counts with IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Escrow UUIDs to permanently delete. Must be archived. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Permanently delete the archived practice escrows I made during training." - "Delete those duplicate archived escrows, but double-check with me before anything is removed forever." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # escrows_batch_restore > Restore multiple archived escrows at once. Restore multiple archived escrows at once. Escrows must be currently archived. Returns success and failure counts with IDs. Restored escrows become active again. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Escrow UUIDs to restore. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Restore the two escrows we archived last week, the deals are back on." - "Unarchive that batch of escrows from March, but confirm the list with me first." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # leads_batch_archive > Archive multiple leads at once. Archive multiple leads at once. Sets lead status to "archived" and marks them as soft-deleted. Returns success and failure counts with IDs. Use [`leads_list`](/tools/leads/leads_list) first to verify the correct lead IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Lead UUIDs to archive. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Archive every lead from the 2024 open house list that never responded." - "Archive those 50 dead sign-call leads, but show me which ones before you do." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # leads_batch_delete > Permanently delete multiple leads that have been archived. Permanently delete multiple leads that have been archived. Leads must be archived before deletion. This action is irreversible. Returns success and failure counts with IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Lead UUIDs to permanently delete. Must be archived. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Permanently delete the archived spam leads that came through the website form." - "Purge those 80 archived junk leads, but double-check with me before deleting them forever." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # leads_batch_restore > Restore multiple archived leads at once. Restore multiple archived leads at once. Resets lead status back to "new" and clears the soft-delete timestamp. Returns success and failure counts with IDs. Restored leads become active again. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Lead UUIDs to restore. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Restore the archived leads from the Maple Grove farm, they're active again." - "Unarchive that batch of website leads, but confirm the list with me first." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # listings_batch_archive > Archive multiple listings at once. Archive multiple listings at once. Sets listing status to "cancelled" and marks them as archived. Returns success and failure counts with IDs. Use [`listings_list`](/tools/listings/listings_list) first to verify the correct listing IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Listing UUIDs to archive. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Archive all the expired listings from last year so my dashboard only shows active ones." - "Archive these three withdrawn listings, but show me the addresses before you proceed." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # listings_batch_delete > Permanently delete multiple listings that have been archived. Permanently delete multiple listings that have been archived. Listings must be archived before deletion. This action is irreversible. Returns success and failure counts with IDs. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Listing UUIDs to permanently delete. Must be archived. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Permanently delete the archived duplicate listings created by the MLS import error." - "Delete those archived test listings for good, but double-check with me before removing them." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # listings_batch_restore > Restore multiple archived listings at once. Restore multiple archived listings at once. Resets listing status back to "active" and clears the archived flag. Returns success and failure counts with IDs. Restored listings become active again. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Listing UUIDs to restore. Max 100. · Max items: 100 · Min items: 1 | ## Example prompts - "Restore the two listings we archived when the sellers paused, they're relisting now." - "Unarchive that batch of listings from the spring cleanup, but confirm the list first." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # Clients > Manage the people you represent — create, update, search, archive, and sync client records. Manage the people you represent — create, update, search, archive, and sync client records. ## Tools (11) | Tool | Type | What it does | | --- | --- | --- | | [`clients_list`](/tools/clients/clients_list) | Read-only | Search for clients. | | [`clients_get`](/tools/clients/clients_get) | Read-only | Get full details of a specific client by ID — contact info, client type, status, representation dates, and tags. | | [`clients_create`](/tools/clients/clients_create) | Creates data | Create a new client (buyer or seller). | | [`clients_update`](/tools/clients/clients_update) | Updates data | Update an existing client's information. | | [`clients_bulk_update`](/tools/clients/clients_bulk_update) | Bulk changes | Update multiple clients at once. | | [`clients_stats`](/tools/clients/clients_stats) | Read-only | Get a summary of all clients including counts by type and status. | | [`clients_archive`](/tools/clients/clients_archive) | Updates data | Archive a client to hide them from active views without deleting their record. | | [`clients_restore`](/tools/clients/clients_restore) | Updates data | Restore a previously archived client back to active views. | | [`clients_find_or_create`](/tools/clients/clients_find_or_create) | Creates data | Look up a client by contact identifier; create one if none exists. | | [`clients_sync_statuses`](/tools/clients/clients_sync_statuses) | Bulk changes | Sync client statuses based on their linked escrow statuses. | | [`clients_delete`](/tools/clients/clients_delete) | Irreversible | Permanently delete a client. | --- # clients_archive > Archive a client to hide them from active views without deleting their record. Archive a client to hide them from active views without deleting their record. Use for past clients you are no longer working with but whose history you want to keep — the client can be restored later with [`clients_restore`](/tools/clients/clients_restore). Returns the archived client record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `client_id` | string | Yes | UUID of the client to archive · Format: UUID | ## Example prompts - "Archive the Pattersons client record now that they've moved out of state." - "Hide Tom Whitfield from my active client list but keep his history." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. ## Previous name This tool was previously published as `archive_client`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # clients_bulk_update > Update multiple clients at once. Update multiple clients at once. Requires CLIENT IDs. Use for batch changes like marking every client on a closed escrow as closed. Returns a summary of the clients updated plus any IDs that were not found. ```text WORKFLOW for updating clients from escrows (DIRECT - no intermediate steps): 1. escrows_list → get relatedIds.clientIds (these ARE client IDs!) 2. clients_bulk_update({ client_ids: relatedIds.clientIds, updates: {...} }) ``` > [!NOTE] > [`escrows_list`](/tools/escrows/escrows_list) now returns BOTH: > - relatedIds.clientIds → use directly with this tool > - relatedIds.contactIds → use with [`contacts_get`](/tools/contacts/contacts_get) (contact_ids) (different entity) ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `client_ids` | array of strings | Yes | Array of CLIENT UUIDs (from [`clients_list`](/tools/clients/clients_list) response.ids). NOT contact IDs from escrows! | | `updates` | object | Yes | Fields to update on all clients | | `updates.status` | enum | No | New status for all clients (active = working with, closed = deal completed, expired = agreement expired, cancelled = client cancelled) · One of: `active`, `closed`, `expired`, `cancelled` | | `updates.client_type` | enum | No | New client type · One of: `buyer`, `seller`, `both` | | `skip_if_already` | boolean | No | If true, skip clients already in target state (default: true). · Default: `true` | ## Example prompts - "Set every client tied to my closed escrows to closed status at once." - "Switch those eight clients to seller type, but show me the list before updating." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. ## Previous name This tool was previously published as `batch_update_clients`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # clients_create > Create a new client (buyer or seller). Create a new client (buyer or seller). Use when someone signs with you or the user asks to add a client directly — to promote an existing lead, use [`leads_convert`](/tools/leads/leads_convert) instead. Call immediately with whatever data the user provides. Do NOT ask for missing fields — the system shows an editable draft card where the user can fill in remaining details. Returns the created client record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `first_name` | string | Yes | First name | | `last_name` | string | Yes | Last name | | `email` | string | No | Email address | | `phone` | string | No | Phone number | | `client_type` | enum | Yes | Type of client · One of: `buyer`, `seller`, `both` | | `budget_min` | number | No | Minimum budget (for buyers) | | `budget_max` | number | No | Maximum budget (for buyers) | | `notes` | string | No | Notes about this client | ## Example prompts - "Add the Garcias as new buyer clients with a budget of 550k to 625k." - "Create a seller client for Tom Whitfield, phone 661-555-0182, he's listing his condo." ## 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. ## Previous name This tool was previously published as `create_client`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # clients_delete > Permanently delete a client. Permanently delete a client. This is IRREVERSIBLE - the client will be hidden from all views including archived. Only use for test data or duplicate records. For normal cleanup, use [`clients_archive`](/tools/clients/clients_archive) instead which is reversible. Returns confirmation of the deletion. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `client_id` | string | Yes | UUID of the client to delete. Use [`clients_get`](/tools/clients/clients_get) first to verify. | ## Example prompts - "Permanently delete that duplicate client record we just archived for Maria Garcia." - "Delete the test client from onboarding for good, but double-check with me before deleting." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # clients_find_or_create > Look up a client by contact identifier; create one if none exists. Look up a client by contact identifier; create one if none exists. Single-call idempotent path for "promote this contact to a client" intents — prefer this over [`clients_list`](/tools/clients/clients_list) → [`clients_create`](/tools/clients/clients_create) chains. Accepts either contact_id (preferred) or a name/email to resolve against the contact directory first. Returns the client record plus a `created: true|false` flag so the caller can tell whether a new record was inserted. New clients go through the same editable draft flow as [`clients_create`](/tools/clients/clients_create). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_id` | string | No | Existing contact UUID (preferred). | | `first_name` | string | No | Given name when resolving by name. | | `last_name` | string | No | Family name when resolving by name. | | `email` | string | No | Contact email for lookup/creation. | | `phone` | string | No | Contact phone for lookup/creation. | | `client_type` | enum | No | Client type to set when creating (default: buyer). · One of: `buyer`, `seller`, `both` | ## Example prompts - "If Marcus Lee from my contacts isn't already a client, set him up as a buyer." - "Promote the contact Priya Shah to a seller client, or pull her file if she exists." ## 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. ## Previous name This tool was previously published as `find_or_create_client`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # clients_get > Get full details of a specific client by ID — contact info, client type, status, representation dates, and tags. Get full details of a specific client by ID — contact info, client type, status, representation dates, and tags. Use after [`clients_list`](/tools/clients/clients_list) when you need every field for one client. For multiple clients, pass client_ids instead. Returns the complete client record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `client_id` | string | No | UUID of a single client to retrieve · Format: UUID | | `client_ids` | array of strings | No | Array of client UUIDs for batch retrieval (max 100). Use either client_id OR client_ids, not both. · Max items: 100 | ## Example prompts - "Pull up everything we have on Maria Garcia's client file." - "Show me the full details for that buyer client you just found." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `get_client`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # clients_list > Search for clients. Search for clients. Returns IDs only by default for efficiency. Use fields parameter to include additional data. Response includes relatedIds.contactIds for chainable operations. > [!NOTE] > When working with escrows, use relatedIds.clientIds directly with [`clients_bulk_update`](/tools/clients/clients_bulk_update). > The contact_ids parameter is for finding clients by their linked contact - only needed for special cases. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term (searches name, email, phone) | | `client_type` | enum | No | Filter by client type · One of: `buyer`, `seller`, `both` | | `status` | enum | No | Filter by client status (active = working with, closed = deal completed, expired = agreement expired, cancelled = client cancelled) · One of: `active`, `closed`, `expired`, `cancelled` | | `contact_ids` | array of strings | No | Filter to clients linked to these contact IDs. CRITICAL for finding clients from escrow contacts - use escrow relatedIds.contactIds here. | | `is_archived` | boolean or string | No | Filter by archived state. Default: false (active clients only). Pass true to find ARCHIVED clients (e.g. for a restore workflow). Pass "any" to include both. | | `fields` | array of enum | No | Field groups to include. Empty/omitted = IDs only. Options: basic (id, type, status), contact (name, email, phone), financial (budget range), activity (dates), full (all fields). · Values: `basic`, `contact`, `financial`, `activity`, `full` | | `limit` | string | No | Max results. Use a number (e.g. "25") or "all". "all" and any value above 200 are capped at 200 server-side. | ## Example prompts - "Show me all my active buyer clients with their contact info." - "Search my clients for anyone named Garcia and pull their phone numbers." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `search_clients`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # clients_restore > Restore a previously archived client back to active views. Restore a previously archived client back to active views. Use when you resume working with a client you had archived. Returns the restored client record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `client_id` | string | Yes | UUID of the archived client to restore · Format: UUID | ## Example prompts - "Restore the Garcias client file, they're ready to start house hunting again." - "Unarchive that client record for Dana Whitfield I archived last fall." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. ## Previous name This tool was previously published as `restore_client`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # clients_stats > Get a summary of all clients including counts by type and status. Get a summary of all clients including counts by type and status. Use for overview questions. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "How many active buyers versus sellers am I working with right now?" - "Give me a quick summary of my client counts by status." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `get_clients_summary`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # clients_sync_statuses > Sync client statuses based on their linked escrow statuses. Sync client statuses based on their linked escrow statuses. When escrows close, the clients linked to them should be marked as 'closed'. This tool handles the ENTIRE workflow in ONE call: finds all clients linked to escrows with the specified status who are still marked active, then updates them. ALWAYS use dry_run=true FIRST to preview what would be updated before making actual changes. Returns the list of clients that would be (or were) updated. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `dry_run` | boolean | No | REQUIRED FIRST STEP: Set true to preview changes without making them. Set false to execute the sync. | | `escrow_status` | enum | No | Which escrow status to sync from. closed=successful transactions, cancelled/fell_through=unsuccessful (default: closed) · One of: `closed`, `cancelled`, `fell_through` | ## Example prompts - "Sync my client statuses so everyone whose escrow closed gets marked closed." - "Preview which active clients would flip to closed from finished escrows before making changes." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # clients_update > Update an existing client's information. Update an existing client's information. Only provided fields are updated — omitted fields remain unchanged. Common uses: change status or client type, fix contact details, adjust representation dates. Returns the updated client record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `client_id` | string | Yes | UUID of the client to update · Format: UUID | | `first_name` | string | No | Updated first name | | `last_name` | string | No | Updated last name | | `email` | string | No | Updated email | | `phone` | string | No | Updated phone | | `status` | enum | No | Updated status (active = working with, closed = deal completed, expired = agreement expired, cancelled = client cancelled, inactive = paused) · One of: `active`, `closed`, `expired`, `cancelled`, `inactive` | | `notes` | string | No | Notes to add | ## Example prompts - "Change Dana Whitfield's phone number to 661-555-0147 on her client record." - "Mark the Hendersons client file as closed now that their purchase recorded." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. ## Previous name This tool was previously published as `update_client`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # Commission ledger > Track agent commission payouts per escrow — list, inspect, and update ledger entries from pending through paid. Track agent commission payouts per escrow — list, inspect, and update ledger entries from pending through paid. ## Tools (4) | Tool | Type | What it does | | --- | --- | --- | | [`commission_ledger_create`](/tools/commission-ledger/commission_ledger_create) | Creates data | Record a commission ledger entry — the payment-tracking record for a deal commission (status, projected/actual payout dates, check number). | | [`commission_ledger_list`](/tools/commission-ledger/commission_ledger_list) | Read-only | List commission ledger entries visible to the caller, newest first. | | [`commission_ledger_get`](/tools/commission-ledger/commission_ledger_get) | Read-only | Get the full details of a single commission ledger entry by its ID — amounts, splits, status, payout dates, and the linked escrow. | | [`commission_ledger_update`](/tools/commission-ledger/commission_ledger_update) | Updates data | Update mutable fields of a commission ledger entry — typically advancing status (pending → processing → paid), recording the actual payout date / check number, or correcting amounts. | --- # commission_ledger_create > Record a commission ledger entry — the payment-tracking record for a deal commission (status, projected/actual payout dates, check number). Record a commission ledger entry — the payment-tracking record for a deal commission (status, projected/actual payout dates, check number). Use this AFTER [`calculate_commission_split`](/tools/financial/calculate_commission_split) to persist the result so it appears on the agent commission ledger. Requires escrow_id, agent_id, and side. All amounts are optional dollar figures; status defaults to pending. This records a payment to be tracked; it does not move money. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | Yes | Escrow/transaction ID this commission belongs to (escrow IDs are human-readable strings, e.g. "ESC-2026-0142", not UUIDs) | | `agent_id` | string | Yes | UUID of the agent (users.id) who earns this commission · Format: UUID | | `side` | enum | Yes | Which side of the deal this commission is for · One of: `listing`, `buyer`, `both` | | `escrow_number` | string | No | Denormalized escrow/file number for list views | | `property_address` | string | No | Denormalized property address for list views | | `transaction_type` | enum | No | Transaction type · One of: `Sale`, `Lease` | | `agent_name` | string | No | Denormalized agent display name | | `sale_price` | number | No | Sale price in dollars · Min: 0 | | `commission_rate` | number | No | Commission rate (percent, e.g. 2.5) · Min: 0 | | `gross_commission` | number | No | Gross commission in dollars · Min: 0 | | `brokerage_split` | number | No | Brokerage split percentage · Min: 0 | | `agent_commission` | number | No | Agent share of the commission in dollars · Min: 0 | | `brokerage_commission` | number | No | Brokerage share of the commission in dollars · Min: 0 | | `referral_fee` | number | No | Referral fee owed in dollars (default 0) · Min: 0 | | `referral_agent` | string | No | Name of the referring agent/company | | `transaction_fee` | number | No | Flat brokerage transaction/admin fee in dollars (default 0) · Min: 0 | | `net_commission` | number | No | Net commission to the agent in dollars · Min: 0 | | `tax_withheld` | boolean | No | Whether tax is withheld on this payout (default false) | | `tax_rate` | number | No | Tax withholding rate percentage (default 0) · Min: 0 | | `status` | enum | No | Payment status (default "pending") · One of: `pending`, `processing`, `paid`, `cancelled` | | `projected_payout_date` | string | No | Projected payout date (YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `notes` | string | No | Free-text notes about this commission | ## Example prompts - "Add a new record under commission ledger." ## 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. --- # commission_ledger_get > Get the full details of a single commission ledger entry by its ID — amounts, splits, status, payout dates, and the linked escrow. Get the full details of a single commission ledger entry by its ID — amounts, splits, status, payout dates, and the linked escrow. Use after [`commission_ledger_list`](/tools/commission-ledger/commission_ledger_list) when you need every field for one entry. Scoped to the caller — returns not-found if the entry belongs to another agent outside the caller scope. Returns the complete ledger entry. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | Yes | UUID of the commission ledger entry · Format: UUID | ## Example prompts - "Pull up the details on one of my commission ledger." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # commission_ledger_list > List commission ledger entries visible to the caller, newest first. List commission ledger entries visible to the caller, newest first. Standard agents see only their own entries; brokers/team leads see their brokerage/team. Use to review upcoming or past commission payouts, or to find an entry's ID before updating it. Filter by status, agent, side, and payout-date range. Returns a paginated summary (id, escrow_number, property_address, side, agent_name, amounts, status, payout dates). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Free-text search across escrow number, property address, and agent name | | `status` | enum | No | Filter by payment status · One of: `pending`, `processing`, `paid`, `cancelled` | | `agent_id` | string | No | Filter by agent UUID (users.id) · Format: UUID | | `side` | enum | No | Filter by deal side · One of: `listing`, `buyer`, `both` | | `start_date` | string | No | Only entries with a payout date on/after this date (YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `end_date` | string | No | Only entries with a payout date on/before this date (YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `limit` | number | No | Max results (default 25, cap 100) · Max: 100 · Min: 1 | | `offset` | number | No | Skip N records for pagination (default 0) · Min: 0 | ## Example prompts - "Show me my commission ledger." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # commission_ledger_update > Update mutable fields of a commission ledger entry — typically advancing status (pending → processing → paid), recording the actual payout date / check number, or correcting amounts. Update mutable fields of a commission ledger entry — typically advancing status (pending → processing → paid), recording the actual payout date / check number, or correcting amounts. Use as payouts move through processing. Setting status to paid without an actual_payout_date stamps the current date automatically. Only entries the caller can see may be updated. Returns the updated ledger entry. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | Yes | UUID of the commission ledger entry to update · Format: UUID | | `status` | enum | No | New payment status · One of: `pending`, `processing`, `paid`, `cancelled` | | `sale_price` | number | No | Corrected sale price in dollars · Min: 0 | | `commission_rate` | number | No | Corrected commission rate (percent) · Min: 0 | | `brokerage_split` | number | No | Corrected brokerage split percentage · Min: 0 | | `gross_commission` | number | No | Corrected gross commission in dollars · Min: 0 | | `agent_commission` | number | No | Corrected agent commission in dollars · Min: 0 | | `net_commission` | number | No | Corrected net commission in dollars · Min: 0 | | `referral_fee` | number | No | Corrected referral fee in dollars · Min: 0 | | `transaction_fee` | number | No | Corrected transaction fee in dollars · Min: 0 | | `projected_payout_date` | string | No | Projected payout date (YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `actual_payout_date` | string | No | Actual payout date (YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `check_number` | string | No | Check number for the payout | | `deposit_account` | string | No | Deposit account the payout went to | | `notes` | string | No | Free-text notes about this commission | ## Example prompts - "Update one of my commission ledger." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # Communication drafts > Draft emails, text messages, and call scripts for your review — nothing is sent until you approve it. Draft emails, text messages, and call scripts for your review — nothing is sent until you approve it. ## Tools (3) | Tool | Type | What it does | | --- | --- | --- | | [`draft_email`](/tools/communication/draft_email) | Draft only | Draft an email for the user to review and send. | | [`draft_sms`](/tools/communication/draft_sms) | Draft only | Draft an SMS text message for the user to review and send. | | [`draft_call_script`](/tools/communication/draft_call_script) | Draft only | Draft a phone call script for the user to reference during a call. | --- # draft_call_script > Draft a phone call script for the user to reference during a call. Draft a phone call script for the user to reference during a call. Use this when the user asks you to prepare talking points, a call script, or help them plan a phone conversation. The script will appear as an interactive card in the chat with a Copy button and a Log Call button. Include a clear opening, key talking points, and suggested close. Tailor the script to real estate contexts: listing presentations, offer discussions, follow-ups, check-ins, etc. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_name` | string | Yes | Full name of the person being called. · Max length: 200 | | `phone` | string | No | Phone number to call. Format: (555) 123-4567 or 5551234567. · Format: Phone number | | `purpose` | string | Yes | Brief purpose of the call. E.g., "Follow up on offer", "Listing presentation", "Check-in after closing". · Max length: 500 | | `script` | string | Yes | The full call script. Include greeting, key discussion points, objection handling, and closing. · Max length: 10000 | | `talking_points` | array of strings | No | Key talking points as a bulleted list. Quick-reference items the agent can glance at during the call. · Max items: 20 | | `contact_id` | string | No | UUID of the contact being called. Used to link the call log after the conversation. · Format: UUID | ## Example prompts - "Prep a call script for my listing presentation with the Whitfields tonight." - "Give me talking points for calling the Garcias about lowering their price to 589k." ## Safety **Draft only.** Prepares a draft for your review — nothing is sent until you approve it. --- # draft_email > Draft an email for the user to review and send. Draft an email for the user to review and send. Use this when the user asks you to compose, write, or draft an email to a contact, lead, client, or any person. The email will appear as an interactive card in the chat where the user can review, edit, and send it via their connected Gmail account. > [!IMPORTANT] > Always look up the recipient's email address first using [`contacts_list`](/tools/contacts/contacts_list) or [`leads_list`](/tools/leads/leads_list) before drafting. Include context from the conversation (property addresses, dates, amounts) to make the email specific and useful. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `to` | string | Yes | Recipient email address. Look up via [`contacts_list`](/tools/contacts/contacts_list) or [`leads_list`](/tools/leads/leads_list) first. · Format: Email address | | `cc` | string | No | CC email address(es), comma-separated if multiple. | | `bcc` | string | No | BCC email address(es), comma-separated if multiple. | | `subject` | string | Yes | Email subject line. Be specific and professional. · Max length: 500 | | `body` | string | Yes | Email body text. Use professional real estate tone. Can include markdown formatting. · Max length: 50000 | | `html_body` | string | No | Optional HTML version of the email body for rich formatting. | | `contact_id` | string | No | UUID of the contact being emailed. Helps link the communication for CRM tracking. · Format: UUID | | `related_entity_type` | enum | No | Type of related entity if this email is about a specific transaction or listing. · One of: `escrow`, `listing`, `appointment`, `deal` | | `related_entity_id` | string | No | UUID of the related entity (escrow, listing, etc.). · Format: UUID | ## Example prompts - "Draft an email to the Garcias confirming Saturday's showing at 412 Birchwood Ln." - "Write an email to my lender contact about the appraisal coming in 15k low." ## Safety **Draft only.** Prepares a draft for your review — nothing is sent until you approve it. --- # draft_sms > Draft an SMS text message for the user to review and send. Draft an SMS text message for the user to review and send. Use this when the user asks you to text, message, or send an SMS to a contact or lead. The message will appear as an interactive card in the chat where the user can review, edit, and send it via Twilio. > [!IMPORTANT] > SMS messages should be concise (under 160 characters for a single segment). Always look up the recipient's phone number first using [`contacts_list`](/tools/contacts/contacts_list) or [`leads_list`](/tools/leads/leads_list). The recipient must have active SMS consent on file before sending. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `to` | string | Yes | Recipient phone number. Look up via [`contacts_list`](/tools/contacts/contacts_list) or [`leads_list`](/tools/leads/leads_list) first. Format: (555) 123-4567 or 5551234567. · Format: Phone number | | `body` | string | Yes | SMS message body. Keep concise — 160 chars = 1 segment. Over 160 splits into multiple segments which cost more. · Max length: 1600 | | `contact_id` | string | No | UUID of the contact being texted. Required for consent verification and CRM tracking. · Format: UUID | | `related_entity_type` | enum | No | Type of related entity if this text is about a specific transaction or listing. · One of: `escrow`, `listing`, `appointment`, `deal` | | `related_entity_id` | string | No | UUID of the related entity (escrow, listing, etc.). · Format: UUID | ## Example prompts - "Text Marcus Lee a quick reminder about tomorrow's 10am walkthrough at 67 Maple Ct." - "Draft a short text to the Hendersons letting them know their offer was accepted." ## Safety **Draft only.** Prepares a draft for your review — nothing is sent until you approve it. --- # Composite workflows > One-call shortcuts that combine several steps, like creating an escrow together with its client records. One-call shortcuts that combine several steps, like creating an escrow together with its client records. ## Tools (3) | Tool | Type | What it does | | --- | --- | --- | | [`create_escrow_with_clients`](/tools/composite/create_escrow_with_clients) | Creates data | Create an escrow AND create/link buyers and sellers in ONE atomic transaction. | | [`log_showing_with_feedback`](/tools/composite/log_showing_with_feedback) | Creates data | Log a property showing AND capture client feedback in ONE call. | | [`create_listing_from_escrow`](/tools/composite/create_listing_from_escrow) | Creates data | Create a new listing pre-populated with data from a closed escrow. | --- # create_escrow_with_clients > Create an escrow AND create/link buyers and sellers in ONE atomic transaction. Create an escrow AND create/link buyers and sellers in ONE atomic transaction. Use this when opening a new transaction where clients don't exist yet — it's equivalent to calling [`lookup_address`](/tools/utility/lookup_address) → [`clients_create`](/tools/clients/clients_create) (×N) → [`escrows_create`](/tools/escrows/escrows_create), but in a single operation that rolls back completely if any step fails. > [!CAUTION] > representation_type determines which parties are YOUR CLIENTS — only add the party you represent. If representation_type='buyer', only add buyers (sellers are just contacts). If 'seller', only add sellers. If 'dual', add both. Returns the created escrow with all linked client IDs. After creation, use [`get_contingency_deadlines`](/tools/deadline/get_contingency_deadlines) to calculate key dates. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `property_address` | string | Yes | Street address (required). Use [`lookup_address`](/tools/utility/lookup_address) first for verified data. | | `display_address` | string | No | Display address if different (e.g., with unit number) | | `city` | string | No | City name (from [`lookup_address`](/tools/utility/lookup_address)) | | `state` | string | No | State abbreviation (e.g., "CA") · Format: Two-letter state code | | `zip_code` | string | No | ZIP code · Format: ZIP code | | `county` | string | No | County name — important for transfer tax calculations | | `latitude` | number | No | Latitude coordinate (from [`lookup_address`](/tools/utility/lookup_address)) | | `longitude` | number | No | Longitude coordinate (from [`lookup_address`](/tools/utility/lookup_address)) | | `purchase_price` | number | Yes | Purchase price in dollars (required) · Min: 0 | | `buyer_commission` | number | No | Buyer agent commission in dollars · Min: 0 | | `buyer_commission_percentage` | number | No | Buyer agent commission as percentage (e.g., 2.5) · Max: 100 · Min: 0 | | `seller_commission` | number | No | Seller agent commission in dollars · Min: 0 | | `seller_commission_percentage` | number | No | Seller agent commission as percentage · Max: 100 · Min: 0 | | `representation_type` | enum | Yes | Who YOU represent. CRITICAL: buyer=only add buyers as clients, seller=only add sellers, dual=add both (required) · One of: `buyer`, `seller`, `dual` | | `acceptance_date` | string | No | Contract acceptance date. Used to calculate contingency deadlines. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `closing_date` | string | No | Expected closing date. Typically 30-45 days from acceptance. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `buyers` | array of objects | No | Array of buyer info. ONLY add if representation_type is "buyer" or "dual". These become YOUR CLIENT records. | | `buyers[].first_name` | string | Yes | Buyer first name (required) | | `buyers[].last_name` | string | Yes | Buyer last name (required) | | `buyers[].email` | string | No | Buyer email · Format: Email address | | `buyers[].phone` | string | No | Buyer phone | | `sellers` | array of objects | No | Array of seller info. ONLY add if representation_type is "seller" or "dual". These become YOUR CLIENT records. | | `sellers[].first_name` | string | Yes | Seller first name (required) | | `sellers[].last_name` | string | Yes | Seller last name (required) | | `sellers[].email` | string | No | Seller email · Format: Email address | | `sellers[].phone` | string | No | Seller phone | ## Example prompts - "Open escrow on 412 Birchwood Ln at 615k, I represent buyers Maria and Luis Garcia." - "Set up a new transaction for 88 Calloway Dr at 745k with my sellers, the Hendersons." ## 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. --- # create_listing_from_escrow > Create a new listing pre-populated with data from a closed escrow. Create a new listing pre-populated with data from a closed escrow. Use when a past client is selling their home (the one they bought through you). Copies property address, coordinates, and links to the seller client automatically. WORKFLOW: For seller representation on a property you previously helped buy, this saves data entry by pulling from the closed escrow. You still need to set listing_price, bedrooms, bathrooms, and other listing-specific fields. Returns the created listing with seller client linked. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | Yes | UUID of the closed escrow to copy address from. Use [`escrows_list`](/tools/escrows/escrows_list) status=closed to find. · Format: UUID | | `seller_client_id` | string | No | UUID of the seller client. Often the buyer from the original escrow. · Format: UUID | | `listing_price` | number | Yes | Listing price in dollars (required) · Min: 0 | | `mls_number` | string | No | MLS number if already listed | | `bedrooms` | number | No | Number of bedrooms · Min: 0 | | `bathrooms` | number | No | Number of bathrooms · Min: 0 | | `square_feet` | number | No | Square footage · Min: 0 | | `property_type` | enum | No | Type of property · One of: `single_family`, `condo`, `townhouse`, `multi_family`, `land`, `commercial` | | `description` | string | No | Property description for MLS | | `listing_status` | enum | No | Initial listing status (default: coming_soon) · One of: `coming_soon`, `active` | | `listing_date` | string | No | Date listing goes live (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `expiration_date` | string | No | Listing expiration date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | ## Example prompts - "The Hendersons are selling the home they bought through me, start a listing at 689k." - "Spin up a coming soon listing from the closed escrow on 412 Birchwood Ln at 599k." ## 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. --- # 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`](/tools/appointments/appointments_create) → [`appointments_update`](/tools/appointments/appointments_update) (status=completed) → [`log_call`](/tools/deadline/log_call) (with feedback notes). Returns the showing record with feedback. Use [`listings_list`](/tools/listings/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`](/tools/clients/clients_list) to find. · Format: UUID | | `listing_id` | string | No | UUID of the listing being shown. Use [`listings_list`](/tools/listings/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. --- # Contacts > Your wider address book — everyone you know, whether or not they are a client yet. Your wider address book — everyone you know, whether or not they are a client yet. ## Tools (8) | Tool | Type | What it does | | --- | --- | --- | | [`contacts_create`](/tools/contacts/contacts_create) | Creates data | Create a new contact in the CRM. | | [`contacts_list`](/tools/contacts/contacts_list) | Read-only | Search for contacts by name, email, phone, or other criteria. | | [`contacts_update`](/tools/contacts/contacts_update) | Updates data | Update an existing contact's information. | | [`contacts_get`](/tools/contacts/contacts_get) | Read-only | Get full details of a specific contact by their ID — names, phones, emails, address, tags, and linked records. | | [`contacts_archive`](/tools/contacts/contacts_archive) | Updates data | Archive a contact to hide them from active views without deleting their record. | | [`contacts_restore`](/tools/contacts/contacts_restore) | Updates data | Restore a previously archived contact back to active views. | | [`contacts_delete`](/tools/contacts/contacts_delete) | Irreversible | Permanently delete a contact. | | [`contacts_stats`](/tools/contacts/contacts_stats) | Read-only | Get aggregate statistics for all contacts: counts by status (homeowner/non_homeowner), counts by role (sphere/lead/client), and total portfolio value. | --- # contacts_archive > Archive a contact to hide them from active views without deleting their record. Archive a contact to hide them from active views without deleting their record. Archived contacts can be restored later with [`contacts_restore`](/tools/contacts/contacts_restore). Use this for contacts you no longer work with but want to keep their history. Returns the archived contact record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_id` | string | Yes | UUID of the contact to archive. Use [`contacts_list`](/tools/contacts/contacts_list) to find the ID if unknown. | ## Example prompts - "Archive my old stager contact since she retired last month." - "Hide the contractor Bill Hayes from my active contacts but keep his history." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # contacts_create > Create a new contact in the CRM. Create a new contact in the CRM. Call immediately with whatever data the user provides. Do NOT ask for missing fields — the system shows an editable draft card where the user can fill in remaining details. > [!NOTE] > For clients with signed representation agreements, use [`clients_find_or_create`](/tools/clients/clients_find_or_create) instead. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `first_name` | string | Yes | First name of the contact | | `last_name` | string | Yes | Last name of the contact | | `email` | string | No | Email address | | `phone` | string | No | Phone number | | `company` | string | No | Company or organization name | | `notes` | string | No | Notes about this contact | ## Example prompts - "Add my new lender contact Sarah Kim from Pacific Trust, phone 661-555-0134." - "Save inspector Dave Romero, dave@romeroinspections.com, to my contact directory." ## 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. ## Previous name This tool was previously published as `create_contact`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # contacts_delete > Permanently delete a contact. Permanently delete a contact. This is IRREVERSIBLE - the contact will be hidden from all views including archived. Only use for test data or duplicate records. For normal cleanup, use [`contacts_archive`](/tools/contacts/contacts_archive) instead which is reversible. Returns confirmation of the deletion. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_id` | string | Yes | UUID of the contact to delete. Use [`contacts_get`](/tools/contacts/contacts_get) first to verify. | ## Example prompts - "Permanently delete the duplicate contact card for Sarah Kim that got imported twice." - "Delete that archived test contact for good, but double-check with me before removing it." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # contacts_get > Get full details of a specific contact by their ID — names, phones, emails, address, tags, and linked records. Get full details of a specific contact by their ID — names, phones, emails, address, tags, and linked records. Use after [`contacts_list`](/tools/contacts/contacts_list) when you need every field for one contact. For multiple contacts, pass contact_ids instead. Returns the complete contact record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_id` | string | No | UUID of a single contact to retrieve · Format: UUID | | `contact_ids` | array of strings | No | Array of contact UUIDs for batch retrieval (max 100). Use either contact_id OR contact_ids, not both. · Max items: 100 | ## Example prompts - "Pull up the full contact card for Dave Romero." - "Show me everything we have on file for my escrow officer Linda Tran." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `get_contact`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # contacts_list > Search for contacts by name, email, phone, or other criteria. Search for contacts by name, email, phone, or other criteria. Use to find existing contacts in the CRM before creating a new one, or to look up a contact's ID for other tools. Returns matching contacts with their IDs and core contact fields. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term (searches name, email, phone) | | `limit` | number | No | Maximum number of results to return (default 10) | ## Example prompts - "Search my contacts for anyone named Romero." - "Find the phone number for my title rep Sarah Kim." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `search_contacts`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # contacts_restore > Restore a previously archived contact back to active views. Restore a previously archived contact back to active views. Reverses the effect of [`contacts_archive`](/tools/contacts/contacts_archive). Use this when a contact re-engages or was archived by mistake. Returns the restored contact record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_id` | string | Yes | UUID of the contact to restore. Must be currently archived. | ## Example prompts - "Restore Bill Hayes to my active contacts, he's taking jobs again." - "Unarchive the photographer contact I archived by accident last week." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # contacts_stats > Get aggregate statistics for all contacts: counts by status (homeowner/non_homeowner), counts by role (sphere/lead/client), and total portfolio value. Get aggregate statistics for all contacts: counts by status (homeowner/non_homeowner), counts by role (sphere/lead/client), and total portfolio value. Use this for dashboard metrics and network analysis. Does NOT return individual contact records - use [`contacts_list`](/tools/contacts/contacts_list) for that. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "How many homeowners versus non-homeowners are in my contact database?" - "Break down my contacts by sphere, lead, and client and show total portfolio value." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # contacts_update > Update an existing contact's information. Update an existing contact's information. Only provided fields are updated — omitted fields remain unchanged. Common uses: fix a phone number or email, update the address, adjust tags. Returns the updated contact record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_id` | string | Yes | UUID of the contact to update · Format: UUID | | `first_name` | string | No | New first name | | `last_name` | string | No | New last name | | `email` | string | No | New email address | | `phone` | string | No | New phone number | | `company` | string | No | New company name | | `notes` | string | No | Notes to add or update | ## Example prompts - "Update Dave Romero's phone number to 661-555-0190 in my contacts." - "Change Sarah Kim's company to Golden Valley Lending and add a note she moved firms." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. ## Previous name This tool was previously published as `update_contact`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # Deadlines & transaction tracking > Contingency deadlines, alerts, escrow checklists, call logging, follow-up reminders, and open-house logging. Contingency deadlines, alerts, escrow checklists, call logging, follow-up reminders, and open-house logging. ## Tools (7) | Tool | Type | What it does | | --- | --- | --- | | [`get_contingency_deadlines`](/tools/deadline/get_contingency_deadlines) | Read-only | Calculate contingency dates (inspection, appraisal, loan, closing) for an escrow. | | [`get_deadline_alerts`](/tools/deadline/get_deadline_alerts) | Read-only | Get upcoming deadlines across ALL active escrows. | | [`get_escrow_checklist`](/tools/deadline/get_escrow_checklist) | Read-only | Get a transaction checklist tailored to your representation type (buyer, seller, or dual agency). | | [`log_call`](/tools/deadline/log_call) | Logs activity | Log a phone call with a contact, lead, or escrow party for CRM tracking. | | [`get_follow_up_reminders`](/tools/deadline/get_follow_up_reminders) | Read-only | Get contacts and leads that need follow-up for daily prospecting and client management. | | [`create_open_house`](/tools/deadline/create_open_house) | Creates data | Schedule an open house event for a listing. | | [`log_open_house_visitor`](/tools/deadline/log_open_house_visitor) | Creates data | Log a visitor at an open house to capture their information. | --- # create_open_house > Schedule an open house event for a listing. Schedule an open house event for a listing. Creates a special appointment of type "open_house" linked to the listing for marketing and visitor tracking. Provide EITHER listing_id to link to an existing listing OR property_address for a one-off event. Types: public (general public), broker (agents only), twilight (evening showing), mega (large event with multiple agents). After creating, use [`log_open_house_visitor`](/tools/deadline/log_open_house_visitor) during the event to capture attendee information and automatically create leads. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `listing_id` | string | No | UUID of the listing this open house is for. Use [`listings_list`](/tools/listings/listings_list) to find ID. · Format: UUID | | `property_address` | string | No | Property address if no listing record exists. One of listing_id or property_address required. | | `start_time` | string | Yes | Start date and time. Examples: "2025-01-25T13:00:00" for 1 PM, "2025-01-25T10:00:00" for 10 AM. (ISO 8601 format, e.g., 2025-01-22T14:30:00Z) · Format: Date-time (ISO 8601) | | `end_time` | string | No | End date and time. Typical duration: 2-4 hours for public, 1-2 hours for broker open. (ISO 8601 format, e.g., 2025-01-22T14:30:00Z) · Format: Date-time (ISO 8601) | | `open_house_type` | enum | No | Type of open house. public=general public (most common), broker=agent preview, twilight=evening showing, mega=large event. · One of: `public`, `broker`, `twilight`, `mega` | | `notes` | string | No | Notes or special instructions. Examples: "Parking in rear", "No shoes inside", "Refreshments provided". · Max length: 2000 | ## Example prompts - "Schedule a public open house at 412 Birchwood Ln this Saturday from 1 to 4." - "Set up a broker preview at 88 Marlowe Ct Tuesday at 10, note parking in rear." ## 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. --- # get_contingency_deadlines > Calculate contingency dates (inspection, appraisal, loan, closing) for an escrow. Calculate contingency dates (inspection, appraisal, loan, closing) for an escrow. ALL ARGUMENTS ARE OPTIONAL. With NO arguments, defaults to the user's most-recent active escrow — call this directly when the user asks "what are my deadlines" or "show me contingency dates" without specifying an escrow. Pass escrow_id to target a specific escrow, OR acceptance_date to compute hypothetically. Day counts default to CAR standards (inspection 17, appraisal 17, loan 21, closing 30); override only if non-standard periods were negotiated. Returns calculated dates only — not legal advice. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `acceptance_date` | string | No | OPTIONAL. Contract acceptance date. If omitted, uses most-recent active escrow's acceptance date. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `escrow_id` | string | No | OPTIONAL. Escrow UUID. If omitted, defaults to most-recent active escrow. Pass to target a specific escrow. · Format: UUID | | `inspection_days` | number | No | Inspection contingency days. CAR default: 17 days. Common alternatives: 10, 14, or waived (0). · Max: 60 · Min: 0 | | `appraisal_days` | number | No | Appraisal contingency days. CAR default: 17 days. Often shortened in competitive markets. · Max: 60 · Min: 0 | | `loan_days` | number | No | Loan contingency days. CAR default: 21 days. Cash deals typically 0. · Max: 60 · Min: 0 | | `closing_days` | number | No | Days from acceptance to close. CAR default: 30 days. Range: 21 (fast) to 60 (complex). · Max: 120 · Min: 0 | ## Example prompts - "What are my contingency deadlines on the 412 Birchwood Ln escrow?" - "If acceptance is May 20 with a 10 day inspection, when do contingencies expire?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # get_deadline_alerts > Get upcoming deadlines across ALL active escrows. Get upcoming deadlines across ALL active escrows. ALL ARGUMENTS ARE OPTIONAL — call with NO args for the standard daily/weekly review (default: 14 days ahead, includes past due). Use this directly when the user asks "what's due", "deadline alerts", "what's coming up", or "what's past due". Pass escrow_id only to filter to one escrow. Returns contingencies + closing dates with days until due (negative = past due) and urgency. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `days_ahead` | number | No | How many days ahead to look for upcoming deadlines. Default: 14 days. Use 7 for weekly review, 30 for monthly planning. · Max: 90 · Min: 1 | | `include_past_due` | boolean | No | Include past due deadlines in results. Default: true. Critical for catching missed deadlines. | | `escrow_id` | string | No | Filter to a specific escrow. If not provided, returns deadlines from ALL active escrows. · Format: UUID | ## Example prompts - "What deadlines are coming up across all my escrows in the next two weeks?" - "Anything past due or closing soon that I need to handle this week?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # get_escrow_checklist > Get a transaction checklist tailored to your representation type (buyer, seller, or dual agency). Get a transaction checklist tailored to your representation type (buyer, seller, or dual agency). Use at contract acceptance to see what's ahead, or mid-transaction to check what's still open. Returns common transaction tasks with suggested due dates calculated from acceptance and closing dates based on standard CAR contract timelines. This is a general reference checklist — not a comprehensive legal compliance tool. Your broker or transaction coordinator can advise on the specific tasks and disclosures required for each transaction. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `representation_type` | enum | No | Who you represent determines the checklist. buyer=BRBC tasks, seller=listing/disclosure tasks, dual=both sets. Default: buyer. · One of: `buyer`, `seller`, `dual` | | `escrow_id` | string | No | Escrow UUID to get dates from. If provided, acceptance_date and closing_date are read from the escrow record. · Format: UUID | | `acceptance_date` | string | No | Contract acceptance date for calculating task due dates. Required if escrow_id not provided. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `closing_date` | string | No | Expected closing date. Required if escrow_id not provided. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | ## Example prompts - "Build me a buyer side checklist for the Garcias escrow on 412 Birchwood Ln." - "We listed 88 Marlowe Ct, acceptance June 3, closing July 6, what seller tasks are due?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # get_follow_up_reminders > Get contacts and leads that need follow-up for daily prospecting and client management. Get contacts and leads that need follow-up for daily prospecting and client management. Returns people who: (1) have scheduled follow-ups due today or past due, (2) haven't been contacted in X days (configurable). Essential for maintaining relationships and not letting leads go cold. Results are sorted by urgency — past due first, then scheduled follow-ups, then stale contacts. Use this every morning to build your call list. For leads, you can filter by status to focus on new/contacted leads vs qualified ones. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `days_since_contact` | number | No | Show contacts/leads not contacted in X days. Default: 7 days. Use 14 for less aggressive follow-up. · Max: 365 · Min: 1 | | `include_scheduled` | boolean | No | Include people with scheduled follow-ups due. Default: true. Set false to only see stale contacts. | | `lead_status` | enum | No | Filter leads by status. new=fresh leads, contacted=in touch, qualified=ready to transact, all=all active leads. Default: all. · One of: `new`, `contacted`, `qualified`, `all` | | `limit` | number | No | Maximum results to return. Default: 20. Use higher for comprehensive review. · Max: 100 · Min: 1 | ## Example prompts - "Who needs a follow up today? Build my morning call list." - "Show me leads I have not touched in the last 14 days." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # log_call > Log a phone call with a contact, lead, or escrow party for CRM tracking. Log a phone call with a contact, lead, or escrow party for CRM tracking. > [!IMPORTANT] > This creates a permanent call log record — use this to track ALL phone communications for follow-up history and compliance. Provide EITHER contact_id, lead_id, OR phone_number to identify who was called. Outcomes track the call result for follow-up automation. If outcome is 'callback_requested' or 'scheduled_appointment', the follow_up_date and follow_up_notes are especially important. Call logs appear in the contact/lead activity timeline and can be used for prospecting reports. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_id` | string | No | UUID of the contact called. Use [`contacts_list`](/tools/contacts/contacts_list) to find ID if unknown. · Format: UUID | | `lead_id` | string | No | UUID of the lead called. Use [`leads_list`](/tools/leads/leads_list) to find ID if unknown. · Format: UUID | | `escrow_id` | string | No | UUID of related escrow if this call was about a specific transaction. · Format: UUID | | `phone_number` | string | No | Phone number called. Use if you do not have a contact_id or lead_id. Format: (555) 123-4567 or 5551234567. · Format: Phone number | | `direction` | enum | No | Call direction. outbound=you called them, inbound=they called you. Default: outbound. · One of: `inbound`, `outbound` | | `outcome` | enum | Yes | Result of the call. Required for proper follow-up tracking. Use connected for live conversations, voicemail for messages left. · One of: `connected`, `voicemail`, `no_answer`, `busy`, `wrong_number`, `callback_requested`, `not_interested`, `scheduled_appointment`, `other` | | `duration_minutes` | number | No | Call duration in minutes. Helps track engagement time for reporting. · Max: 480 · Min: 0 | | `subject` | string | No | Brief subject/reason for call. Examples: "Listing follow-up", "Offer update", "Market check-in". · Max length: 200 | | `notes` | string | No | Detailed notes from the call. What was discussed, action items, client concerns, etc. · Max length: 5000 | | `follow_up_date` | string | No | Date to follow up with this person. Especially important for callback_requested or voicemail outcomes. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `follow_up_notes` | string | No | Specific notes for the follow-up. What to discuss, preparation needed, etc. · Max length: 1000 | At least one of the following is required: `contact_id`, `lead_id`, `phone_number`. ## Example prompts - "Log a 12 minute call with Maria Garcia about the appraisal, she wants a callback Friday." - "Note that I left a voicemail for the lender on the Birchwood escrow this morning." ## Safety **Logs activity.** Adds an activity log entry. Your existing records are not changed. --- # log_open_house_visitor > Log a visitor at an open house to capture their information. Log a visitor at an open house to capture their information. AUTOMATICALLY creates a LEAD record with the open house as the source — this is your primary lead generation tool at open houses. Capture as much information as possible: buyer_status helps prioritize follow-up, working_with_agent indicates if they're represented, price_range helps match them to listings. Link to open_house_id (appointment) or listing_id. After the open house, use [`get_hot_leads`](/tools/reporting/get_hot_leads) to see which visitors should be contacted first based on their engagement score. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `open_house_id` | string | No | UUID of the open house appointment. Links visitor to specific event for tracking. · Format: UUID | | `listing_id` | string | No | UUID of the listing. Alternative if no open_house_id — useful for walk-in visitors. · Format: UUID | | `first_name` | string | Yes | Visitor first name. Required for lead creation. · Max length: 100 · Min length: 1 | | `last_name` | string | Yes | Visitor last name. Required for lead creation. · Max length: 100 · Min length: 1 | | `email` | string | No | Visitor email. Critical for follow-up — try to get this! · Format: Email address | | `phone` | string | No | Visitor phone. Important for quick follow-up calls. · Format: Phone number | | `buyer_status` | enum | No | Buyer readiness. pre_approved and ready_to_buy are highest priority. just_looking may be long-term nurture. · One of: `just_looking`, `starting_search`, `actively_searching`, `ready_to_buy`, `pre_approved` | | `working_with_agent` | boolean | No | Already working with another agent? If true, be mindful of ethics rules. | | `interested_in_property` | boolean | No | Interested in THIS specific property? Helps gauge if they are a buyer lead or just curious. | | `price_range_min` | number | No | Minimum price range. Helps match to other listings. · Min: 0 | | `price_range_max` | number | No | Maximum price range. Helps match to other listings. · Min: 0 | | `interest_level` | enum | No | Overall interest level in the property. Helps prioritize follow-up after the open house. · One of: `low`, `medium`, `high` | | `notes` | string | No | Additional notes. Feedback on property, what they are looking for, timeline, etc. · Max length: 2000 | At least one of the following is required: `email`, `phone`. ## Example prompts - "Log visitor Dana Whitfield from today's open house, pre approved and shopping 600k to 700k." - "Add visitor Tom Nguyen from the Birchwood open house, he already has an agent." ## 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. --- # Deals (vendor pipeline) > Track vendor deals through the vendor sales pipeline — create, update, stats, and lifecycle operations. Track vendor deals through the vendor sales pipeline — create, update, stats, and lifecycle operations. ## Tools (8) | Tool | Type | What it does | | --- | --- | --- | | [`deals_list`](/tools/deals/deals_list) | Read-only | Search for vendor deals by title, status, vendor type, or deal type. | | [`deals_get`](/tools/deals/deals_get) | Read-only | Get full details of a vendor deal by UUID, including contact info, vendor type, deal type, financial details (amount, fee, commission), linked partner, linked escrow, property address, notes, and tags. | | [`deals_create`](/tools/deals/deals_create) | Creates data | Create a new vendor deal to track a transaction or payment with a vendor partner. | | [`deals_update`](/tools/deals/deals_update) | Updates data | Update an existing vendor deal's information or status. | | [`deals_stats`](/tools/deals/deals_stats) | Read-only | Get aggregate statistics for vendor deals: total count, counts by status, counts by payment status, total revenue, total fees, total commissions, counts by vendor type. | | [`deals_archive`](/tools/deals/deals_archive) | Updates data | Archive a vendor deal to hide it from active views without deleting it. | | [`deals_restore`](/tools/deals/deals_restore) | Updates data | Restore a previously archived vendor deal back to active views. | | [`deals_delete`](/tools/deals/deals_delete) | Irreversible | Permanently delete a vendor deal. | --- # deals_archive > Archive a vendor deal to hide it from active views without deleting it. Archive a vendor deal to hide it from active views without deleting it. Archived deals can be restored later with [`deals_restore`](/tools/deals/deals_restore). Use this for completed or cancelled deals you want to declutter from your dashboard. Returns the archived record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `deal_id` | string | Yes | UUID of the deal to archive. Use [`deals_list`](/tools/deals/deals_list) to find. · Format: UUID | ## Example prompts - "Archive the cancelled photography deal at 17 Quail Run so it stops cluttering my dashboard." - "Move the paid Birchwood inspection deal out of my active pipeline, keep it recoverable." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # deals_create > Create a new vendor deal to track a transaction or payment with a vendor partner. Create a new vendor deal to track a transaction or payment with a vendor partner. WORKFLOW: 1) Optionally use [`contacts_list`](/tools/contacts/contacts_list) to find the contact, [`partners_list`](/tools/partners/partners_list) to find the partner, and [`escrows_list`](/tools/escrows/escrows_list) to find the escrow 2) Create the deal with vendor_type, deal details, and financial info. Returns the created deal with ID and display_id. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_id` | string | No | UUID of an existing contact for this deal. Use [`contacts_list`](/tools/contacts/contacts_list) to find. · Format: UUID | | `vendor_type` | string | Yes | Type of vendor (e.g. lender, inspector, escrow_officer, title_rep, appraiser, contractor, photographer) | | `partner_id` | string | No | UUID of the linked partner. Use [`partners_list`](/tools/partners/partners_list) to find. · Format: UUID | | `escrow_service_id` | string | No | UUID of the linked escrow service record. · Format: UUID | | `escrow_id` | string | No | UUID of the linked escrow. Use [`escrows_list`](/tools/escrows/escrows_list) to find. · Format: UUID | | `title` | string | No | Title or description for this deal (e.g. "Home Inspection - 123 Main St") | | `deal_type` | string | No | Type of deal (e.g. inspection, appraisal, escrow_service, title_service, photography, staging, repair) | | `amount` | number | No | Total deal amount in dollars · Min: 0 | | `fee` | number | No | Service fee amount in dollars · Min: 0 | | `commission_amount` | number | No | Commission or referral amount in dollars · Min: 0 | | `property_address` | string | No | Property address associated with this deal | | `notes` | string | No | Additional notes about the deal | | `tags` | array of strings | No | Tags for categorization (e.g. ["rush", "repeat-client", "discounted"]) | ## Example prompts - "Create a new deal for a home inspection at 412 Birchwood Ln, 650 dollars." - "Track a staging job for the Garcias listing, 2400 total with a 200 referral fee." ## 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. --- # deals_delete > Permanently delete a vendor deal. Permanently delete a vendor deal. This is IRREVERSIBLE - the deal will be hidden from all views including archived. The deal must be archived first. For normal cleanup, use [`deals_archive`](/tools/deals/deals_archive) instead, which is reversible. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `deal_id` | string | Yes | UUID of the deal to delete. Must be archived first. Use [`deals_get`](/tools/deals/deals_get) to verify. · Format: UUID | ## Example prompts - "Permanently delete the duplicate inspection deal we created twice for 412 Birchwood Ln." - "Erase that test deal completely, but double-check with me before deleting anything." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # deals_get > Get full details of a vendor deal by UUID, including contact info, vendor type, deal type, financial details (amount, fee, commission), linked partner, linked escrow, property address, notes, and tags. Get full details of a vendor deal by UUID, including contact info, vendor type, deal type, financial details (amount, fee, commission), linked partner, linked escrow, property address, notes, and tags. Returns all fields. If you don't have the UUID, use [`deals_list`](/tools/deals/deals_list) first. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `deal_id` | string | Yes | UUID of the deal. Use [`deals_list`](/tools/deals/deals_list) to find IDs. · Format: UUID | ## Example prompts - "Pull up the full details on the 412 Birchwood Ln inspection deal." - "What is the fee and payment status on the Marlowe Ct appraisal deal?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # deals_list > Search for vendor deals by title, status, vendor type, or deal type. Search for vendor deals by title, status, vendor type, or deal type. Returns pagination info (total_count, has_more, offset, limit). Results include: id, display_id, title, vendor_type, deal_type, status, payment_status, amount, fee, commission_amount, property_address, contact info, created_at. Filter by status (pending/in_progress/completed/invoiced/paid/cancelled/disputed), payment_status (unpaid/invoiced/paid/refunded), vendor_type, or deal_type. For a specific deal by ID, use [`deals_get`](/tools/deals/deals_get) instead. For aggregate stats, use [`deals_stats`](/tools/deals/deals_stats). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term - matches against title, property_address, notes (case-insensitive partial match) | | `status` | enum | No | Filter by status. pending=awaiting start, in_progress=work underway, completed=work done, invoiced=invoice sent, paid=payment received, cancelled=deal off, disputed=payment issue (default: all) · One of: `all`, `pending`, `in_progress`, `completed`, `invoiced`, `paid`, `cancelled`, `disputed` | | `payment_status` | enum | No | Filter by payment status (default: all) · One of: `all`, `unpaid`, `invoiced`, `paid`, `refunded` | | `vendor_type` | string | No | Filter by vendor type (e.g. lender, inspector, escrow_officer, title_rep, appraiser, contractor, photographer) | | `deal_type` | string | No | Filter by deal type (e.g. inspection, appraisal, escrow_service, title_service, photography, staging, repair) | | `vertical` | string | No | Filter by industry vertical (e.g., lending, insurance, inspection) | | `date_from` | string | No | Show deals created on or after this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `date_to` | string | No | Show deals created on or before this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `archived` | boolean | No | Include archived deals (default: false) | | `limit` | number | No | Maximum results (default: 50, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "Show me all my unpaid inspection deals from the last 30 days." - "Pull up every invoiced deal that has not been paid yet." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # deals_restore > Restore a previously archived vendor deal back to active views. Restore a previously archived vendor deal back to active views. Reverses the effect of [`deals_archive`](/tools/deals/deals_archive). Returns the restored record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `deal_id` | string | Yes | UUID of the deal to restore. Must be currently archived. · Format: UUID | ## Example prompts - "Bring back the archived appraisal deal for 88 Marlowe Ct, the client reopened it." - "Restore the Quail Run photography deal I archived last week." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # deals_stats > Get aggregate statistics for vendor deals: total count, counts by status, counts by payment status, total revenue, total fees, total commissions, counts by vendor type. Get aggregate statistics for vendor deals: total count, counts by status, counts by payment status, total revenue, total fees, total commissions, counts by vendor type. Use this for dashboard metrics and financial summaries. Does NOT return individual records - use [`deals_list`](/tools/deals/deals_list) for that. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `period` | enum | No | Time period for stats (default: 1_month) · One of: `1_day`, `1_week`, `1_month`, `3_months`, `1_year`, `ytd`, `all` | ## Example prompts - "Give me this month's deal totals, revenue, fees, and commissions by vendor type." - "How many of my deals are still unpaid versus paid this quarter?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # deals_update > Update an existing vendor deal's information or status. ```text Update an existing vendor deal's information or status. Only provided fields are updated - omitted fields remain unchanged. Common uses: status change (pending->in_progress->completed->invoiced->paid), update financial details, link to escrow. Returns the updated deal record. ``` ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `deal_id` | string | Yes | UUID of the deal to update (required). Use [`deals_list`](/tools/deals/deals_list) to find. · Format: UUID | | `contact_id` | string | No | Updated contact ID. Use [`contacts_list`](/tools/contacts/contacts_list) to find. · Format: UUID | | `vendor_type` | string | No | Updated vendor type | | `partner_id` | string | No | Updated partner ID. Use [`partners_list`](/tools/partners/partners_list) to find. · Format: UUID | | `escrow_service_id` | string | No | Updated escrow service record ID. · Format: UUID | | `escrow_id` | string | No | Updated escrow ID. Use [`escrows_list`](/tools/escrows/escrows_list) to find. · Format: UUID | | `title` | string | No | Updated title | | `deal_type` | string | No | Updated deal type | | `status` | enum | No | Updated status · One of: `pending`, `in_progress`, `completed`, `invoiced`, `paid`, `cancelled`, `disputed` | | `payment_status` | enum | No | Updated payment status · One of: `unpaid`, `invoiced`, `paid`, `refunded` | | `amount` | number | No | Updated deal amount · Min: 0 | | `fee` | number | No | Updated service fee · Min: 0 | | `commission_amount` | number | No | Updated commission amount · Min: 0 | | `property_address` | string | No | Updated property address | | `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). | | `started_at` | string | No | Timestamp the deal work started. Usually set alongside status=in_progress. (ISO 8601 format, e.g., 2025-01-22T14:30:00Z) · Format: Date-time (ISO 8601) | | `completed_at` | string | No | Timestamp the deal was completed. Usually set alongside status=completed. (ISO 8601 format, e.g., 2025-01-22T14:30:00Z) · Format: Date-time (ISO 8601) | | `paid_date` | string | No | Date the deal was paid out. Usually set alongside payment_status=paid. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `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 Birchwood Ln inspection deal as completed and invoiced." - "The Marlowe Ct appraisal got paid today, update its payment status and paid date." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # Documents > Read AI risk-analysis results for documents uploaded to a transaction. Read AI risk-analysis results for documents uploaded to a transaction. ## Tools (2) | Tool | Type | What it does | | --- | --- | --- | | [`documents_get_risks`](/tools/documents/documents_get_risks) | Read-only | Get the latest AI risk analysis for a document the agent owns. | | [`documents_list`](/tools/documents/documents_list) | Read-only | List the documents attached to a specific entity (escrow, listing, client, lead, or appointment). | --- # documents_get_risks > Get the latest AI risk analysis for a document the agent owns. Get the latest AI risk analysis for a document the agent owns. Returns findings (each with id, severity P0/P1/P2, title, description, citation, recommendation), summary counts (p0_count, p1_count, p2_count, overall_severity, headline), and the analysis state (pending / in_review / acknowledged / escalated / resolved). Returns null if no analysis has been run on this document yet — the agent must trigger analysis from the web app first (Risk Analysis modal on the document detail page). The findings are AI-generated risk signals, not legal advice; always defer to the agent's broker or attorney for actual decisions. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `document_id` | string | Yes | The document_id (e.g. "doc_7022796200ff"). Get this from the documents tool or from an escrow's document list. · Max length: 50 · Min length: 1 | ## Example prompts - "Any red flags in the risk analysis on the Birchwood purchase agreement?" - "Show me the P0 findings from the AI review of the Garcias disclosure packet." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # documents_list > List the documents attached to a specific entity (escrow, listing, client, lead, or appointment). List the documents attached to a specific entity (escrow, listing, client, lead, or appointment). Returns each document id (pass it to [`documents_get_risks`](/tools/documents/documents_get_risks)), filename, original_name, document_type, category, mime_type, file_size, requires_signature, signed_at, is_primary_contract, and created_at, newest first. Use this to see what is on file for a transaction (the RPA, TDS, NHD, pre-approval on an escrow). Read-only; returns only documents the agent can access under their tenant scope. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `entity_type` | enum | Yes | The kind of record the documents are attached to. · One of: `escrow`, `listing`, `client`, `lead`, `appointment` | | `entity_id` | string | Yes | The id of the escrow, listing, client, lead, or appointment. · Max length: 50 · Min length: 1 | | `limit` | number | No | Max documents to return (default 50). · Max: 200 · Min: 1 | ## Example prompts - "Show me my documents." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # DRE license lookup > Look up a California DRE real-estate license via the official DRE API. Look up a California DRE real-estate license via the official DRE API. ## Tools (1) | Tool | Type | What it does | | --- | --- | --- | | [`lookup_dre_license`](/tools/dre-license/lookup_dre_license) | External lookup | Look up a California DRE (Department of Real Estate) license by ID. | --- # lookup_dre_license > Look up a California DRE (Department of Real Estate) license by ID. Look up a California DRE (Department of Real Estate) license by ID. Returns comprehensive license information: license type (salesperson/broker/corporation), licensee name, license status (active/inactive/expired/cancelled), expiration date, business and mailing addresses, and for salespersons: their responsible broker information. Works for all license types: salesperson (starts with 01 or 02), broker (01 or 02), corporation (01). Use this to verify agents you are working with or to look up cooperating brokers. Note: This makes an external API call to the DRE — expect a 1-3 second response time. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `license_id` | string | Yes | The 8-digit DRE license ID. Examples: "02203217" (salesperson), "01910265" (corporation), "00123456" (broker). Leading zeros required. | ## Example prompts - "Verify DRE license 02203217 for the buyers agent writing the Birchwood offer." - "Check whether license 01910265 is still active and when it expires." ## Safety **External lookup.** A read-only lookup against a service outside ActuallyCare. It may take a few seconds and is subject to that service’s availability. --- # Engagements (vendor pipeline) > Track vendor engagements and interactions — create, update, stats, and lifecycle operations. Track vendor engagements and interactions — create, update, stats, and lifecycle operations. ## Tools (8) | Tool | Type | What it does | | --- | --- | --- | | [`engagements_list`](/tools/engagements/engagements_list) | Read-only | Search for vendor engagements by title, status, vendor type, or engagement type. | | [`engagements_get`](/tools/engagements/engagements_get) | Read-only | Get full details of a vendor engagement by UUID, including contact info, vendor type, engagement type, schedule, location, meeting URL, notes, tags, and linked prospect. | | [`engagements_create`](/tools/engagements/engagements_create) | Creates data | Create a new vendor engagement to track a meeting, call, or event with a vendor. | | [`engagements_update`](/tools/engagements/engagements_update) | Updates data | Update an existing vendor engagement's information or status. | | [`engagements_stats`](/tools/engagements/engagements_stats) | Read-only | Get aggregate statistics for vendor engagements: total count, counts by status, counts by vendor type, counts by engagement type, upcoming engagements count. | | [`engagements_archive`](/tools/engagements/engagements_archive) | Updates data | Archive a vendor engagement to hide it from active views without deleting it. | | [`engagements_restore`](/tools/engagements/engagements_restore) | Updates data | Restore a previously archived vendor engagement back to active views. | | [`engagements_delete`](/tools/engagements/engagements_delete) | Irreversible | Permanently delete a vendor engagement. | --- # engagements_archive > Archive a vendor engagement to hide it from active views without deleting it. Archive a vendor engagement to hide it from active views without deleting it. Archived engagements can be restored later with [`engagements_restore`](/tools/engagements/engagements_restore). Use this for completed or cancelled engagements you want to declutter from your dashboard. Returns the archived record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `engagement_id` | string | Yes | UUID of the engagement to archive. Use [`engagements_list`](/tools/engagements/engagements_list) to find. · Format: UUID | ## Example prompts - "Archive the cancelled March networking event so it is off my dashboard." - "Clear that completed office visit with Pacific Escrow out of my active list." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # 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`](/tools/contacts/contacts_list) to find the contact and [`prospects_list`](/tools/prospects/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`](/tools/contacts/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`](/tools/prospects/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. --- # engagements_delete > Permanently delete a vendor engagement. Permanently delete a vendor engagement. This is IRREVERSIBLE - the engagement will be hidden from all views including archived. The engagement must be archived first. For normal cleanup, use [`engagements_archive`](/tools/engagements/engagements_archive) instead, which is reversible. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `engagement_id` | string | Yes | UUID of the engagement to delete. Must be archived first. Use [`engagements_get`](/tools/engagements/engagements_get) to verify. · Format: UUID | ## Example prompts - "Permanently delete the duplicate lunch entry I accidentally logged twice for Marcus Hale." - "Wipe that test engagement entirely, but double-check with me before deleting it." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # engagements_get > Get full details of a vendor engagement by UUID, including contact info, vendor type, engagement type, schedule, location, meeting URL, notes, tags, and linked prospect. Get full details of a vendor engagement by UUID, including contact info, vendor type, engagement type, schedule, location, meeting URL, notes, tags, and linked prospect. Returns all fields. If you don't have the UUID, use [`engagements_list`](/tools/engagements/engagements_list) first. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `engagement_id` | string | Yes | UUID of the engagement. Use [`engagements_list`](/tools/engagements/engagements_list) to find IDs. · Format: UUID | ## Example prompts - "Pull up the details for my Thursday lunch with the title rep." - "What is the meeting link and agenda for my training with the lender team Friday?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # engagements_list > Search for vendor engagements by title, status, vendor type, or engagement type. Search for vendor engagements by title, status, vendor type, or engagement type. Returns pagination info (total_count, has_more, offset, limit). Results include: id, display_id, title, vendor_type, engagement_type, status, scheduled_date, scheduled_time, duration_minutes, location, contact info, created_at. Filter by status (proposed/scheduled/in_progress/follow_up/completed/cancelled), vendor_type, or engagement_type. For a specific engagement by ID, use [`engagements_get`](/tools/engagements/engagements_get) instead. For aggregate stats, use [`engagements_stats`](/tools/engagements/engagements_stats). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term - matches against title, notes (case-insensitive partial match) | | `status` | enum | No | Filter by status. proposed=suggested, scheduled=confirmed, in_progress=happening now, follow_up=needs follow-up, completed=done, cancelled=not happening (default: all) · One of: `all`, `proposed`, `scheduled`, `in_progress`, `follow_up`, `completed`, `cancelled` | | `vendor_type` | string | No | Filter by vendor type (e.g. lender, inspector, escrow_officer, title_rep, appraiser, contractor, photographer) | | `engagement_type` | string | No | Filter by engagement type (e.g. coffee_meeting, lunch, phone_call, office_visit, networking_event, training, co_marketing) | | `date_from` | string | No | Show engagements scheduled on or after this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `date_to` | string | No | Show engagements scheduled on or before this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `archived` | boolean | No | Include archived engagements (default: false) | | `limit` | number | No | Maximum results (default: 50, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "What meetings do I have scheduled with lenders this month?" - "List every coffee meeting still sitting in proposed status that needs confirming." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # engagements_restore > Restore a previously archived vendor engagement back to active views. Restore a previously archived vendor engagement back to active views. Reverses the effect of [`engagements_archive`](/tools/engagements/engagements_archive). Returns the restored record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `engagement_id` | string | Yes | UUID of the engagement to restore. Must be currently archived. · Format: UUID | ## Example prompts - "Restore the archived coffee meeting with Marcus Hale, we are rescheduling it." - "Bring back the training engagement I archived by mistake yesterday." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # engagements_stats > Get aggregate statistics for vendor engagements: total count, counts by status, counts by vendor type, counts by engagement type, upcoming engagements count. Get aggregate statistics for vendor engagements: total count, counts by status, counts by vendor type, counts by engagement type, upcoming engagements count. Use this for dashboard metrics. Does NOT return individual records - use [`engagements_list`](/tools/engagements/engagements_list) for that. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `period` | enum | No | Time period for stats (default: 1_month) · One of: `1_day`, `1_week`, `1_month`, `3_months`, `1_year`, `ytd`, `all` | ## Example prompts - "How many vendor engagements did I complete this month, broken down by type?" - "How many upcoming meetings do I have on the books versus cancelled this month?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # engagements_update > Update an existing vendor engagement's information or status. ```text 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`](/tools/engagements/engagements_list) to find. · Format: UUID | | `contact_id` | string | No | Updated contact ID. Use [`contacts_list`](/tools/contacts/contacts_list) to find. · Format: UUID | | `vendor_type` | string | No | Updated vendor type | | `prospect_id` | string | No | Updated prospect ID. Use [`prospects_list`](/tools/prospects/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. --- # Entity links > Create, list, and remove relationships between any two records — link contacts to escrows, leads to listings, and more. Create, list, and remove relationships between any two records — link contacts to escrows, leads to listings, and more. ## Tools (3) | Tool | Type | What it does | | --- | --- | --- | | [`entity_links_list`](/tools/entity-links/entity_links_list) | Read-only | List entity links for a specific entity. | | [`entity_links_create`](/tools/entity-links/entity_links_create) | Creates data | Create a cross-vertical link between two entities (e.g., link a lending deal to a real estate escrow). | | [`entity_links_delete`](/tools/entity-links/entity_links_delete) | Irreversible | Remove a cross-vertical entity link by its ID. | --- # entity_links_create > Create a cross-vertical link between two entities (e.g., link a lending deal to a real estate escrow). Create a cross-vertical link between two entities (e.g., link a lending deal to a real estate escrow). Both entities must exist. The link is queryable from either side. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `source_type` | enum | Yes | Source entity type · One of: `escrow`, `deal`, `lead`, `client`, `appointment`, `listing` | | `source_id` | string | Yes | Source entity ID | | `source_vertical` | string | Yes | Source entity vertical (e.g., real_estate, lending) | | `target_type` | enum | Yes | Target entity type · One of: `escrow`, `deal`, `lead`, `client`, `appointment`, `listing` | | `target_id` | string | Yes | Target entity ID | | `target_vertical` | string | Yes | Target entity vertical | | `link_type` | enum | No | Type of relationship (default: related) · One of: `related`, `converted_from`, `depends_on`, `parent_of`, `assigned_to` | | `notes` | string | No | Optional notes about the relationship | ## Example prompts - "Link the Hale lending deal to the Birchwood Ln escrow so they cross-reference." - "Connect the Marlowe Ct inspection deal to its escrow, note they share the same client." ## 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. --- # entity_links_delete > Remove a cross-vertical entity link by its ID. Remove a cross-vertical entity link by its ID. Use when two records were linked by mistake or the relationship no longer applies — the linked records themselves are not touched. Find the link ID with [`entity_links_list`](/tools/entity-links/entity_links_list) first. Returns confirmation of the deletion. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | Yes | UUID of the entity link to remove · Format: UUID | ## Example prompts - "Unlink the Hale lending deal from the old Birchwood escrow, it points to the wrong file." - "Remove the bad link between those two records, but double-check with me before deleting." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # entity_links_list > List entity links for a specific entity. List entity links for a specific entity. Query by entity_type + entity_id to find all related entities across verticals — for example all deals linked to an escrow, or all escrows linked to a deal. Use before creating a link (to avoid duplicates) or to navigate between related records. Returns the matching links with both endpoints and each link's ID. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term (not used for entity links — use entity_type + entity_id instead) | | `entity_type` | enum | No | Type of entity to find links for · One of: `escrow`, `deal`, `lead`, `client`, `appointment`, `listing` | | `entity_id` | string | No | ID of the entity to find links for | | `source_type` | string | No | Filter by source entity type | | `source_id` | string | No | Filter by source entity ID | ## Example prompts - "What deals are linked to the escrow at 412 Birchwood Ln?" - "Show me every record connected to the Hale lending deal across verticals." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Escrows > Your transactions from contract to close — create, search, update, and manage escrows. Your transactions from contract to close — create, search, update, and manage escrows. ## Tools (9) | Tool | Type | What it does | | --- | --- | --- | | [`escrows_list`](/tools/escrows/escrows_list) | Read-only | Search for escrows. | | [`escrows_get`](/tools/escrows/escrows_get) | Read-only | Get full details of a specific escrow by ID — property, parties, key dates, price, commission, and status. | | [`escrows_create`](/tools/escrows/escrows_create) | Creates data | Create a new escrow/transaction record. | | [`escrows_update`](/tools/escrows/escrows_update) | Updates data | Update an existing escrow/transaction record. | | [`escrows_stats`](/tools/escrows/escrows_stats) | Read-only | Get a summary of all escrows including counts by status and upcoming closings. | | [`escrow_parties_sync`](/tools/escrows/escrow_parties_sync) | Updates data | Synchronize the buyer and/or seller client rosters for an escrow. | | [`escrows_archive`](/tools/escrows/escrows_archive) | Updates data | Archive an escrow to hide it from active views without deleting it. | | [`escrows_restore`](/tools/escrows/escrows_restore) | Updates data | Restore a previously archived escrow back to active views. | | [`escrows_delete`](/tools/escrows/escrows_delete) | Irreversible | Permanently delete an escrow. | --- # escrow_parties_sync > Synchronize the buyer and/or seller client rosters for an escrow. ```text Synchronize the buyer and/or seller client rosters for an escrow. Pass the full desired roster for each side; the tool compares it against the escrow's current parties and adds/removes as needed. Provide only the sides you want to change — omit a side to leave it unchanged, pass an empty array to remove all parties on that side. Each client_id must already exist (use clients_create or clients_find_or_create first). Returns { added, removed, buyers, sellers } summarizing the change and the resulting rosters. ``` ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | Yes | UUID of the escrow whose roster you want to sync. | | `buyers` | array of strings | No | Desired buyer client UUIDs (full set — compared against the current roster). Omit to leave buyers unchanged; pass [] to clear. | | `sellers` | array of strings | No | Desired seller client UUIDs (full set — compared against the current roster). Omit to leave sellers unchanged; pass [] to clear. | ## Example prompts - "Add Luis and Maria Garcia as the buyers on the Birchwood Ln escrow." - "Remove the co-buyer from the Marlowe Ct escrow, keep only Dana Whitfield as buyer." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # escrows_archive > Archive an escrow to hide it from active views without deleting it. Archive an escrow to hide it from active views without deleting it. Archived escrows can be restored later with [`escrows_restore`](/tools/escrows/escrows_restore). Use this for completed or abandoned transactions you want to declutter from your dashboard. Returns the archived escrow record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | Yes | UUID of the escrow to archive. Use [`escrows_list`](/tools/escrows/escrows_list) to find the ID if unknown. | ## Example prompts - "Archive the closed Birchwood Ln escrow now that it has funded." - "Move the cancelled Quail Run escrow off my active dashboard without deleting it." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # escrows_create > Create a new escrow/transaction record. Create a new escrow/transaction record. Use when an offer is accepted and a transaction opens — to also create buyer/seller client records in one call, use [`create_escrow_with_clients`](/tools/composite/create_escrow_with_clients) instead. Call immediately with whatever data the user provides. Do NOT ask for missing fields — the system shows an editable draft card where the user can fill in remaining details. Returns the created escrow record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `property_address` | string | Yes | Full property address (street line) | | `city` | string | No | City name | | `state` | string | No | State abbreviation (e.g. "CA") | | `zip_code` | string | No | ZIP code (5 or 9 digit) | | `purchase_price` | number | No | Purchase price in dollars | | `escrow_number` | string | No | Escrow or file number (the escrow's file number, stored as display_id). Must be unique; omit to have one generated. | | `closing_date` | string | No | Expected closing date (YYYY-MM-DD format) | | `escrow_status` | enum | No | Status of the escrow · One of: `active`, `pending`, `closed`, `cancelled` | | `representation_type` | enum | No | Who the agent represents in this transaction · One of: `buyer`, `seller`, `dual` | ## Example prompts - "Open a new escrow for 412 Birchwood Ln, Bakersfield CA 93309, 565000, closing July 15." - "Start an escrow file for the Garcias at 88 Marlowe Ct, escrow number PCH-4471." ## 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. ## Previous name This tool was previously published as `create_escrow`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # escrows_delete > Permanently delete an escrow. Permanently delete an escrow. This is IRREVERSIBLE - the escrow will be hidden from all views including archived. Only use for test data or duplicate records. For normal cleanup, use [`escrows_archive`](/tools/escrows/escrows_archive) instead which is reversible. Returns confirmation of the deletion. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | Yes | UUID of the escrow to delete. Use [`escrows_get`](/tools/escrows/escrows_get) first to verify. | ## Example prompts - "Permanently delete the duplicate Birchwood Ln escrow we entered twice last week." - "Get rid of that test escrow for good, but double-check with me before deleting." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # escrows_get > Get full details of a specific escrow by ID — property, parties, key dates, price, commission, and status. Get full details of a specific escrow by ID — property, parties, key dates, price, commission, and status. Use after [`escrows_list`](/tools/escrows/escrows_list) when you need every field for one transaction. For multiple escrows, pass escrow_ids instead. Returns the complete escrow record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | No | UUID of a single escrow to retrieve · Format: UUID | | `escrow_ids` | array of strings | No | Array of escrow UUIDs for batch retrieval (max 100). Use either escrow_id OR escrow_ids, not both. · Max items: 100 | ## Example prompts - "Give me the full file on the Birchwood Ln escrow, every detail." - "Pull up everything on the Garcias escrow, including buyers, sellers, and commission." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `get_escrow`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # escrows_list > Search for escrows. Search for escrows. Returns IDs only by default for efficiency. Response includes relatedIds with BOTH clientIds and contactIds: - relatedIds.clientIds: CLIENT table IDs → use with [`clients_bulk_update`](/tools/clients/clients_bulk_update) - relatedIds.contactIds: CONTACT table IDs → use with [`contacts_get`](/tools/contacts/contacts_get) (contact_ids) ```text WORKFLOW: To mark clients as closed when escrow closes: 1. escrows_list({ status: 'closed' }) → get relatedIds.clientIds 2. clients_bulk_update({ client_ids: relatedIds.clientIds, updates: { status: 'closed' } }) ``` Direct workflow - no intermediate [`clients_list`](/tools/clients/clients_list) step needed! ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term (searches property address, escrow number) | | `status` | enum | No | Filter by escrow status (default: all) · One of: `all`, `active`, `pending`, `closed`, `cancelled`, `fell_through` | | `fields` | array of enum | No | Field groups to include. Empty/omitted = IDs only (most efficient). Options: basic (id, display_id, address, status), dates (closing_date, etc), financial (price, commission), clients (buyers/sellers), location (city, state), property (beds, baths), full (all fields). · Values: `basic`, `dates`, `financial`, `clients`, `location`, `property`, `full` | | `limit` | string or number | No | Max results. Use a number (e.g. "25") or "all". "all" and any value above 200 are capped at 200 server-side. · Max: 200 | | `offset` | number | No | Skip N records for pagination. Use pagination.nextOffset from previous response. | | `slim` | boolean | No | DEPRECATED: Use fields parameter instead. slim=true maps to fields=[] (IDs only). | ## Example prompts - "Which of my escrows are still active right now?" - "Find the escrow for 412 Birchwood Ln and show its closing date and price." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `search_escrows`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # escrows_restore > Restore a previously archived escrow back to active views. Restore a previously archived escrow back to active views. Reverses the effect of [`escrows_archive`](/tools/escrows/escrows_archive). Use this when a transaction needs to be revisited or was archived by mistake. Returns the restored escrow record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | Yes | UUID of the escrow to restore. Must be currently archived. | ## Example prompts - "Restore the Marlowe Ct escrow I archived, the buyers came back." - "Bring the archived Quail Run file back to active, that deal is reviving." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # escrows_stats > Get a summary of all escrows including counts by status and upcoming closings. Get a summary of all escrows including counts by status and upcoming closings. Use for overview questions. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "How many escrows do I have open, and which close in the next two weeks?" - "Give me a quick summary of my escrows by status." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `get_escrow_summary`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # escrows_update > Update an existing escrow/transaction record. Update an existing escrow/transaction record. Only provided fields are updated — omitted fields remain unchanged. Common uses: move key dates, update the price, or change status as the transaction progresses. Returns the updated escrow record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | Yes | UUID of the escrow to update · Format: UUID | | `property_address` | string | No | Updated property address | | `purchase_price` | number | No | Updated purchase price | | `escrow_number` | string | No | Updated escrow number (the escrow's file number, stored as display_id). Must be unique. | | `closing_date` | string | No | Updated closing date (YYYY-MM-DD) | | `escrow_status` | enum | No | Updated status · One of: `active`, `pending`, `closed`, `cancelled`, `fell_through` | ## Example prompts - "Push the Birchwood Ln closing date out to August 1." - "Update the Marlowe Ct purchase price to 612500 after the appraisal renegotiation." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. ## Previous name This tool was previously published as `update_escrow`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # Financial calculators > Pure calculators: seller net sheet, buyer closing costs, mortgage payment, and commission split. Pure calculators: seller net sheet, buyer closing costs, mortgage payment, and commission split. ## Tools (4) | Tool | Type | What it does | | --- | --- | --- | | [`calculate_seller_net_sheet`](/tools/financial/calculate_seller_net_sheet) | Calculator | Calculate estimated seller proceeds after all closing costs. | | [`calculate_buyer_closing_costs`](/tools/financial/calculate_buyer_closing_costs) | Calculator | Calculate estimated buyer closing costs. | | [`calculate_mortgage_payment`](/tools/financial/calculate_mortgage_payment) | Calculator | Calculate estimated monthly mortgage payment with PITI breakdown (Principal, Interest, Taxes, Insurance). | | [`calculate_commission_split`](/tools/financial/calculate_commission_split) | Calculator | Calculate estimated agent net commission after broker split, franchise fees, and transaction fees. | --- # calculate_buyer_closing_costs > Calculate estimated buyer closing costs. Calculate estimated buyer closing costs. Shows buyers their TOTAL CASH needed to close including down payment. Includes: down payment, loan origination fees, appraisal, inspection, title insurance, escrow fees, prepaid insurance, prepaid taxes, and other costs. Loan type affects costs: FHA has mortgage insurance premiums, VA has funding fee, jumbo may have higher fees. Returns itemized breakdown plus total cash needed. > [!NOTE] > These are estimates — actual lender costs may vary. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `purchase_price` | number | Yes | The purchase price of the property (required) · Min: 0 | | `down_payment_pct` | number | No | Down payment as percentage (e.g., 20 for 20%). Affects PMI requirement. · Max: 100 · Min: 0 | | `loan_type` | enum | No | Type of loan. Affects costs: FHA=MIP, VA=funding fee, jumbo=higher fees (default: conventional) · One of: `conventional`, `fha`, `va`, `jumbo` | | `interest_rate` | number | No | Annual interest rate as percentage (e.g., 6.5 for 6.5%). Used for prepaid interest calculation. · Max: 20 · Min: 0 | | `lender_fees` | number | No | Lender origination/processing fees. If not provided, estimated as 1% of loan amount. · Min: 0 | | `appraisal_fee` | number | No | Appraisal fee (default: $600) · Min: 0 | | `inspection_fee` | number | No | Home inspection fee (default: $500) · Min: 0 | | `title_insurance_pct` | number | No | Title insurance as percentage of purchase price (default: 0.5) · Max: 2 · Min: 0 | | `escrow_fee` | number | No | Escrow fee. If not provided, estimated as $2 per $1,000 of purchase price. · Min: 0 | | `prepaid_insurance` | number | No | Prepaid homeowners insurance (typically 1 year). If not provided, estimated. · Min: 0 | | `prepaid_taxes_months` | number | No | Months of property taxes to prepay into escrow (default: 3) · Max: 12 · Min: 0 | | `property_tax_rate` | number | No | Annual property tax rate as percentage (default: 1.1 for CA) · Max: 5 · Min: 0 | | `hoa_monthly` | number | No | Monthly HOA dues — affects prepaid HOA fees (default: 0) · Min: 0 | ## Example prompts - "How much cash do the Nguyens need to close at 565000 with 10 percent down FHA?" - "Estimate buyer closing costs on a 750000 purchase, conventional loan, 20 down, 6.25 rate." ## Safety **Calculator.** Pure math. Reads nothing and writes nothing in your CRM. --- # calculate_commission_split > Calculate estimated agent net commission after broker split, franchise fees, and transaction fees. Calculate estimated agent net commission after broker split, franchise fees, and transaction fees. Use when the user asks what they will actually take home from a sale. Provide gross_commission directly OR calculate from sale_price+commission_pct. Returns itemized estimate of deductions plus net-to-agent amount. > [!NOTE] > This is a simplified estimate — verify all commission calculations with your brokerage accounting. Does not account for referral fees, team splits, E&O, or brokerage caps. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `gross_commission` | number | No | Total gross commission in dollars. Provide this OR sale_price+commission_pct. · Min: 0 | | `commission_pct` | number | No | Commission percentage (used with sale_price to calculate gross_commission) · Max: 10 · Min: 0 | | `sale_price` | number | No | Sale price (used with commission_pct) · Min: 0 | | `broker_split_pct` | number | Yes | Percentage you KEEP after broker split (required, e.g., 80 for 80/20 split means you keep 80%) · Max: 100 · Min: 0 | | `referral_fee_pct` | number | No | Referral fee percentage owed to referring agent/company (default: 0) · Max: 100 · Min: 0 | | `team_split_pct` | number | No | Team lead split percentage if on a team (default: 0) · Max: 100 · Min: 0 | | `transaction_fee` | number | No | Flat transaction/admin fee charged by brokerage (default: 0) · Min: 0 | | `errors_omissions_fee` | number | No | E&O insurance fee per transaction (default: 0) · Min: 0 | | `franchise_fee_pct` | number | No | Franchise fee percentage if applicable (e.g., Keller Williams, RE/MAX) · Max: 10 · Min: 0 | ## Example prompts - "What do I net on a 565000 sale at 2.5 percent with my 80/20 split?" - "Break down my net on 14125 gross with a 70/30 split and 25 percent referral." ## Safety **Calculator.** Pure math. Reads nothing and writes nothing in your CRM. --- # calculate_mortgage_payment > Calculate estimated monthly mortgage payment with PITI breakdown (Principal, Interest, Taxes, Insurance). ```text Calculate estimated monthly mortgage payment with PITI breakdown (Principal, Interest, Taxes, Insurance). Use when a buyer asks what their monthly payment would be for a given price or loan. Includes: P&I, property taxes, homeowners insurance, HOA dues, and PMI if applicable (down payment < 20%). Can calculate from loan_amount OR from purchase_price with down_payment_pct. Returns itemized estimate of each component. NOTE: These are estimates — actual payments depend on lender terms. This is not financial advice. ``` ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `loan_amount` | number | No | Total loan amount in dollars. Provide this OR purchase_price+down_payment_pct. · Min: 0 | | `purchase_price` | number | No | Purchase price (used with down_payment_pct to calculate loan) · Min: 0 | | `down_payment_pct` | number | No | Down payment as percentage (e.g., 20 for 20%) · Max: 100 · Min: 0 | | `interest_rate` | number | Yes | Annual interest rate as percentage (required, e.g., 6.5 for 6.5%) · Max: 20 · Min: 0 | | `loan_term_years` | number | No | Loan term in years (default: 30) · Max: 40 · Min: 1 | | `property_tax_rate` | number | No | Annual property tax rate as percentage (default: 1.1 for CA) · Max: 5 · Min: 0 | | `homeowners_insurance` | number | No | Annual homeowners insurance. If not provided, estimated as 0.35% of purchase price. · Min: 0 | | `hoa_monthly` | number | No | Monthly HOA dues (default: 0) · Min: 0 | | `pmi_rate` | number | No | PMI rate as percentage of loan if down payment < 20% (default: 0.5) · Max: 3 · Min: 0 | | `include_pmi` | boolean | No | Include PMI in calculation. Auto-included if down payment < 20% (default: true if applicable) | ## Example prompts - "What is the monthly PITI on a 452000 loan at 6.5 percent over 30 years?" - "Estimate the payment at 612500, 15 percent down, 6.75 rate, 320 monthly HOA." ## Safety **Calculator.** Pure math. Reads nothing and writes nothing in your CRM. --- # calculate_seller_net_sheet > Calculate estimated seller proceeds after all closing costs. Calculate estimated seller proceeds after all closing costs. Shows sellers what they will NET from their sale. Includes: listing commission, buyer agent commission, title insurance, escrow fees, county/city transfer taxes, loan payoff, HOA fees, repairs/credits, and other costs. CALIFORNIA-SPECIFIC: Uses CA default transfer tax rates (0.11% county). For accurate city transfer tax, provide county name. Returns itemized breakdown of all costs plus estimated net proceeds. > [!NOTE] > These are estimates — actual amounts may vary based on negotiation and specific circumstances. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `sale_price` | number | Yes | The sale price of the property (required) · Min: 0 | | `mortgage_balance` | number | No | Remaining mortgage balance to pay off (default: 0) · Min: 0 | | `listing_commission_pct` | number | No | Listing agent commission percentage (e.g., 2.5 for 2.5%) · Max: 10 · Min: 0 | | `buyer_agent_commission_pct` | number | No | Buyer agent commission percentage (e.g., 2.5 for 2.5%) · Max: 10 · Min: 0 | | `title_insurance_pct` | number | No | Title insurance as percentage of sale price (default: 0.5) · Max: 2 · Min: 0 | | `escrow_fee` | number | No | Escrow fee in dollars. If not provided, estimated as $2 per $1,000 of sale price · Min: 0 | | `transfer_tax_pct` | number | No | County transfer tax percentage (default: 0.11 for CA, $1.10 per $1,000) · Max: 2 · Min: 0 | | `city_transfer_tax_pct` | number | No | City transfer tax percentage if applicable. Some CA cities have additional taxes (e.g., Oakland, Berkeley) · Max: 3 · Min: 0 | | `hoa_fees` | number | No | HOA transfer fees or outstanding dues owed (default: 0) · Min: 0 | | `repairs_credits` | number | No | Repairs or credits to buyer negotiated in contract (default: 0) · Min: 0 | | `other_costs` | number | No | Any other closing costs not listed above (default: 0) · Min: 0 | | `county` | string | No | County name for accurate transfer tax lookup (optional, uses CA default if not provided) | ## Example prompts - "Run a net sheet for the Garcias, 565000 sale, 310000 payoff, 2.5 and 2.5 commission." - "What will the sellers at 88 Marlowe Ct net at 612500 in Kern County?" ## Safety **Calculator.** Pure math. Reads nothing and writes nothing in your CRM. --- # Geographic boundaries > Search regional, neighborhood, and subdivision boundaries by place name. Search regional, neighborhood, and subdivision boundaries by place name. ## Tools (2) | Tool | Type | What it does | | --- | --- | --- | | [`geo_boundary_search`](/tools/geo-boundaries/geo_boundary_search) | Read-only | Search geographic boundaries (regional neighborhoods, neighborhoods, subdivisions) by name. | | [`geo_boundary_parcels`](/tools/geo-boundaries/geo_boundary_parcels) | Read-only | List the assessor parcels inside a geographic boundary (a subdivision, tract, parcel map, neighborhood, city or other boundary id from geo_boundary_search). | --- # geo_boundary_parcels > List the assessor parcels inside a geographic boundary (a subdivision, tract, parcel map, neighborhood, city or other boundary id from geo_boundary_search). List the assessor parcels inside a geographic boundary (a subdivision, tract, parcel map, neighborhood, city or other boundary id from [`geo_boundary_search`](/tools/geo-boundaries/geo_boundary_search)). Returns one page of parcels, each with APN, APN label, membership share, centroid, label point and bbox. Membership comes from the stored parcel-to-boundary relation, so a parcel straddling the line appears with its share (0–1). Pages are keyset: pass the returned next_after as after to get the next page; next_after is null on the last page. Use this to answer "how many lots are in this subdivision" or "which parcels make up this tract"; it does not return owners, addresses or listing data. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `boundary_id` | string | Yes | The boundary id, e.g. from [`geo_boundary_search`](/tools/geo-boundaries/geo_boundary_search). · Format: UUID | | `limit` | integer | No | Parcels per page (1–500). Defaults to 100. · Default: `100` · Max: 500 · Min: 1 | | `after` | string | No | The next_after value from the previous page. Omit for the first page. | ## Example prompts - "List the parcels inside the Seven Oaks subdivision." - "How many parcels are in tract 6243? Show me the first page of APNs." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # geo_boundary_search > Search geographic boundaries (regional neighborhoods, neighborhoods, subdivisions) by name. ```text Search geographic boundaries (regional neighborhoods, neighborhoods, subdivisions) by name. Returns id, kind, name, centroid, and bbox for each match. Useful when the user asks about a named place ("show me The Northwest", "what neighborhood is this in"). Pass the returned id to listings_list as boundary_id to filter listings to the polygon. Results are ordered by kind priority (regional > neighborhood > subdivision) then text-search relevance — so a search for "northwest" surfaces "The Northwest" (regional) above any subdivision with that word in its name. ``` ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | Yes | Search term — matches against boundary name (case-insensitive, full-text-search). · Max length: 80 · Min length: 1 | | `limit` | integer | No | Max results (1–25). Defaults to 10. · Default: `10` · Max: 25 · Min: 1 | ## Example prompts - "Look up the boundary for The Northwest so I can pull listings inside it." - "Which neighborhoods or subdivisions match the name Seven Oaks?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Goals > Set targets like "12 closings this quarter", plan them as milestones, and check milestones off. Set targets like "12 closings this quarter", plan them as milestones, and check milestones off. ## Tools (5) | Tool | Type | What it does | | --- | --- | --- | | [`goals_list`](/tools/goals/goals_list) | Read-only | Search the caller's goals (KPI targets like "12 closings this quarter" or "get my first subscriber"). | | [`goals_get`](/tools/goals/goals_get) | Read-only | Get one goal by UUID with its ordered milestone plan (each milestone: id, name, due_date, sort_order, completed_at) and its plan progress (plan_done, plan_total, plan_pct). | | [`goals_create`](/tools/goals/goals_create) | Creates data | Create a goal for the authenticated user. | | [`goals_update`](/tools/goals/goals_update) | Updates data | Update an existing goal's name, description, target, period, or status. | | [`goals_milestone_complete`](/tools/goals/goals_milestone_complete) | Updates data | Mark one milestone of a goal's plan finished (the headline action — "check off the first milestone on my subscriber goal"). | --- # goals_create > Create a goal for the authenticated user. Create a goal for the authenticated user. Every goal needs a name (it is the heading users see), a metric, a positive target_value, and a period. The five derived metrics have their progress calculated from live CRM data; use metric="manual" for a goal whose number nobody can count for you (e.g. "get my first subscriber") — that is the only metric for which you may pass current_value. The goal is always created FOR the caller: assigning a goal to another user is a web-app action, not an MCP one. Returns the created goal. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `name` | string | Yes | Name of the goal, said the way a person would say it (e.g. "Get my first user to subscribe") | | `metric` | enum | Yes | What the goal counts. Use "manual" when the number is not derivable from CRM data. · One of: `closings`, `gci`, `lead_conversions`, `appointments`, `listings_taken`, `manual` | | `target_value` | number | Yes | The number to reach (dollars for gci, a count otherwise) · Min: 0.01 | | `period_type` | enum | Yes | How long the goal runs · One of: `weekly`, `monthly`, `quarterly`, `annually`, `custom` | | `period_start` | string | Yes | First day of the goal period (YYYY-MM-DD) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `period_end` | string | Yes | Last day of the goal period (YYYY-MM-DD) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `description` | string | No | Optional longer description (max 4000 characters) | | `unit_label` | string | No | Optional unit shown beside the number (max 24 characters, e.g. "listings") | | `current_value` | number | No | Starting value. ONLY valid when metric="manual" — for every other metric the value is calculated from live data and passing it is rejected. · Min: 0 | | `started_on` | string | No | The date the goal was set (YYYY-MM-DD). Defaults to period_start. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | ## Example prompts - "Set a goal of 12 closings this quarter." - "Make a manual goal to get my first newsletter subscriber by the end of the year." ## 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. --- # goals_get > Get one goal by UUID with its ordered milestone plan (each milestone: id, name, due_date, sort_order, completed_at) and its plan progress (plan_done, plan_total, plan_pct). Get one goal by UUID with its ordered milestone plan (each milestone: id, name, due_date, sort_order, completed_at) and its plan progress (plan_done, plan_total, plan_pct). Same derived-metric caveat as [`goals_list`](/tools/goals/goals_list): current_value is returned only for metric="manual". If you don't have the UUID, use [`goals_list`](/tools/goals/goals_list) first. To mark a milestone finished, use [`goals_milestone_complete`](/tools/goals/goals_milestone_complete). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `goal_id` | string | Yes | UUID of the goal. Use [`goals_list`](/tools/goals/goals_list) to find IDs. · Format: UUID | ## Example prompts - "Which milestones are left on my Q4 closings goal?" - "Show me the plan for my first-subscriber goal." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # goals_list > Search the caller's goals (KPI targets like "12 closings this quarter" or "get my first subscriber"). Search the caller's goals (KPI targets like "12 closings this quarter" or "get my first subscriber"). Returns pagination info (total_count, has_more, offset, limit). Each result includes: id, name, metric, target_value, period_type, period_start, period_end, status, accent, created_at, plus plan progress (plan_done, plan_total, plan_pct) counted from the goal's milestones. > [!NOTE] > for the five derived metrics (closings, gci, lead_conversions, appointments, listings_taken) the CURRENT metric value is calculated live by the web app from escrows/leads/appointments/listings and is deliberately NOT returned here — plan progress is. current_value is returned only for metric="manual", where the owner sets the number. Filter by status, metric, or period_type. For one goal plus its milestones, use [`goals_get`](/tools/goals/goals_get). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term — matches against goal name and description (case-insensitive partial match) | | `status` | enum | No | Filter by status (default: all) · One of: `all`, `active`, `paused`, `achieved`, `missed` | | `metric` | enum | No | Filter by the metric the goal targets · One of: `closings`, `gci`, `lead_conversions`, `appointments`, `listings_taken`, `manual` | | `period_type` | enum | No | Filter by period length · One of: `weekly`, `monthly`, `quarterly`, `annually`, `custom` | | `limit` | number | No | Maximum results (default: 50, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "What goals am I working on this quarter?" - "Show me my paused goals." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # goals_milestone_complete > Mark one milestone of a goal's plan finished (the headline action — "check off the first milestone on my subscriber goal"). Mark one milestone of a goal's plan finished (the headline action — "check off the first milestone on my subscriber goal"). Also completes every open checklist step underneath that milestone, in the same transaction, so the plan cannot end up with a done milestone holding open steps. Idempotent in effect — completing an already-complete milestone just refreshes its timestamp. Use [`goals_get`](/tools/goals/goals_get) to find milestone IDs. Only the goal's owner or its author may change the plan. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `goal_id` | string | Yes | UUID of the parent goal (required). Use [`goals_list`](/tools/goals/goals_list) to find. · Format: UUID | | `milestone_id` | string | Yes | UUID of the milestone to complete (required). Use [`goals_get`](/tools/goals/goals_get) to find. · Format: UUID | ## Example prompts - "Check off the first milestone on my subscriber goal." - "I finished the "build the mailing list" milestone. Mark it done." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # goals_update > Update an existing goal's name, description, target, period, or status. Update an existing goal's name, description, target, period, or status. Only provided fields change — omitted fields stay unchanged. Use status="achieved" when the goal is met, "missed" when the period ended short, or "paused" to set it aside. current_value is writable ONLY on a metric="manual" goal. A goal's assignment (who it belongs to) is write-once and cannot be changed here. Returns the updated goal. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `goal_id` | string | Yes | UUID of the goal to update (required). Use [`goals_list`](/tools/goals/goals_list) to find. · Format: UUID | | `name` | string | No | Updated goal name (max 200 characters) | | `description` | string | No | Updated description (max 4000 characters) | | `unit_label` | string | No | Updated unit label (max 24 characters) | | `target_value` | number | No | Updated target number · Min: 0.01 | | `current_value` | number | No | Updated current value. ONLY valid on a metric="manual" goal. · Min: 0 | | `period_type` | enum | No | Updated period length · One of: `weekly`, `monthly`, `quarterly`, `annually`, `custom` | | `period_start` | string | No | Updated first day of the period (YYYY-MM-DD) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `period_end` | string | No | Updated last day of the period (YYYY-MM-DD) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `status` | enum | No | Updated status · One of: `active`, `paused`, `achieved`, `missed` | ## Example prompts - "Mark my September listings goal as achieved." - "Raise my Q4 closings target from 12 to 15." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # Habits > Personal habit trackers — create daily, weekly, or monthly habits, log completions, and review streaks. Personal habit trackers — create daily, weekly, or monthly habits, log completions, and review streaks. ## Tools (5) | Tool | Type | What it does | | --- | --- | --- | | [`habits_list`](/tools/habits/habits_list) | Read-only | Search the authenticated user's habits (daily/weekly/monthly trackers like "Read My Bible", "Go to the Gym"). | | [`habits_get`](/tools/habits/habits_get) | Read-only | Get full details of one habit by UUID, including its per-habit checklist (step_template), tracker schema (tracker_schema), cadence, status, started_on, and best_streak. | | [`habits_create`](/tools/habits/habits_create) | Creates data | Create a new habit to track. | | [`habits_update`](/tools/habits/habits_update) | Updates data | Update an existing habit's name, cadence, status, tagline, or weekly target. | | [`habits_log`](/tools/habits/habits_log) | Updates data | Mark a habit's progress for a day (the headline action — "mark my Bible reading done today"). | --- # habits_create > Create a new habit to track. Create a new habit to track. The checklist and trackers are seeded automatically from the habit_type (bible/gym/throwing/reading/custom). Returns the created habit with its id and display_id (H-####). Cadence defaults to 'daily'. After creating, use [`habits_log`](/tools/habits/habits_log) to mark progress for a day. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `name` | string | Yes | Name of the habit (e.g. "Read My Bible", "Go to the Gym") | | `habit_type` | enum | No | Habit type — seeds the default checklist + trackers (default: custom) · One of: `bible`, `gym`, `throwing`, `reading`, `custom` | | `cadence` | enum | No | How often the habit recurs (default: daily) · One of: `daily`, `weekly`, `monthly` | | `weekly_target` | number | No | For weekly cadence — target sessions per week (e.g. 4 for a gym habit) · Max: 7 · Min: 1 | | `tagline` | string | No | A short reminder of the "why" behind the habit | | `started_on` | string | No | The date the habit started (YYYY-MM-DD). Defaults to unset. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | ## Example prompts - "Add a new record under habits." ## 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. --- # habits_get > Get full details of one habit by UUID, including its per-habit checklist (step_template), tracker schema (tracker_schema), cadence, status, started_on, and best_streak. Get full details of one habit by UUID, including its per-habit checklist (step_template), tracker schema (tracker_schema), cadence, status, started_on, and best_streak. If you don't have the UUID, use [`habits_list`](/tools/habits/habits_list) first. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `habit_id` | string | Yes | UUID of the habit. Use [`habits_list`](/tools/habits/habits_list) to find IDs. · Format: UUID | ## Example prompts - "Pull up the details on one of my habits." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # habits_list > Search the authenticated user's habits (daily/weekly/monthly trackers like "Read My Bible", "Go to the Gym"). Search the authenticated user's habits (daily/weekly/monthly trackers like "Read My Bible", "Go to the Gym"). Returns pagination info (total_count, has_more, offset, limit). Each result includes: id, display_id, name, habit_type, cadence, status, started_on, best_streak, created_at. Filter by status (active/paused/archived) or habit_type. For a single habit's full detail + checklist + trackers, use [`habits_get`](/tools/habits/habits_get). To mark a habit done for a day, use [`habits_log`](/tools/habits/habits_log). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term — matches against habit name and tagline (case-insensitive partial match) | | `status` | enum | No | Filter by status (default: all) · One of: `all`, `active`, `paused`, `archived` | | `habit_type` | string | No | Filter by habit type (e.g. bible, gym, throwing, reading, custom) | | `archived` | boolean | No | Include archived habits (default: false) | | `limit` | number | No | Maximum results (default: 50, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "Show me my habits." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # habits_log > Mark a habit's progress for a day (the headline action — "mark my Bible reading done today"). Mark a habit's progress for a day (the headline action — "mark my Bible reading done today"). Upserts the per-day log: pass done=true to mark the day complete, plus optional checklist steps and tracker metrics. Defaults log_date to today. Idempotent — calling again for the same day updates that day's log. Returns the saved log row. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `habit_id` | string | Yes | UUID of the habit to log (required). Use [`habits_list`](/tools/habits/habits_list) to find. · Format: UUID | | `log_date` | string | No | The day to log (YYYY-MM-DD). Defaults to today. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `done` | boolean | No | Whether the habit was completed for the day (default: true) | | `steps` | object (free-form) | No | Checklist completion as { stepId: boolean } — keys match the habit's step_template ids. | | `metrics` | object (free-form) | No | Tracker values as { trackerKey: value } — keys match the habit's tracker_schema keys. | | `note` | string | No | An optional note for the day | ## Example prompts - "Mark a habit's progress for a day (the headline action — "mark my Bible reading done today") — just ask in plain English." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # habits_update > Update an existing habit's name, cadence, status, tagline, or weekly target. Update an existing habit's name, cadence, status, tagline, or weekly target. Only provided fields are updated — omitted fields stay unchanged. Use status='paused' to pause a habit or status='active' to resume. Returns the updated habit. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `habit_id` | string | Yes | UUID of the habit to update (required). Use [`habits_list`](/tools/habits/habits_list) to find. · Format: UUID | | `name` | string | No | Updated habit name | | `cadence` | enum | No | Updated cadence · One of: `daily`, `weekly`, `monthly` | | `status` | enum | No | Updated status · One of: `active`, `paused`, `archived` | | `weekly_target` | number | No | Updated weekly target · Max: 7 · Min: 1 | | `tagline` | string | No | Updated tagline | ## Example prompts - "Update one of my habits." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # Landing pages > Manage open-house sign-in pages and marketing landing pages, with guardrails enforced server-side. Manage open-house sign-in pages and marketing landing pages, with guardrails enforced server-side. ## Tools (7) | Tool | Type | What it does | | --- | --- | --- | | [`landing_page_create`](/tools/landing-pages/landing_page_create) | Creates data | Create a landing page for an open house sign-in or marketing purpose. | | [`landing_page_edit`](/tools/landing-pages/landing_page_edit) | Creates data + external action | Edit a landing page using natural language. | | [`landing_page_get`](/tools/landing-pages/landing_page_get) | Read-only | Get details of a landing page including status, shortcode URL, view count, submission count, and configuration. | | [`landing_page_publish`](/tools/landing-pages/landing_page_publish) | Updates data | Publish the current draft of a landing page to make it live. | | [`landing_page_revert`](/tools/landing-pages/landing_page_revert) | Irreversible | Revert a landing page draft to the last published version. | | [`landing_page_submissions`](/tools/landing-pages/landing_page_submissions) | Read-only | Get visitor sign-in submissions for a landing page. | | [`generate_open_house_flyer`](/tools/landing-pages/generate_open_house_flyer) | Read-only | Generate a professional PDF flyer for an open house. | --- # generate_open_house_flyer > Generate a professional PDF flyer for an open house. Generate a professional PDF flyer for an open house. Use when preparing marketing for an upcoming open house. Auto-populates from MLS listing data (photos, beds/baths/sqft, price, description), agent profile (headshot, contact info, DRE#), and brokerage brand (logo, colors, disclaimer). Returns a download URL for the PDF. The flyer is print-ready at 8.5" × 11" letter size. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `open_house_id` | string | Yes | UUID of the open house to generate a flyer for. | ## Example prompts - "Make a print-ready flyer for Sunday's open house at 412 Birchwood Ln." - "Generate a PDF flyer with my headshot and brokerage logo for the Garcia open house." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # landing_page_create > Create a landing page for an open house sign-in or marketing purpose. Create a landing page for an open house sign-in or marketing purpose. Optionally link it to an open house by ID to create a visitor sign-in page with a QR code. The page is created as a draft — use [`landing_page_publish`](/tools/landing-pages/landing_page_publish) to make it live. Returns: id, shortcode, publicUrl, status, title. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `title` | string | Yes | Page title (e.g. "Sign In — 123 Main St"). Required. | | `open_house_id` | string | No | UUID of the open house to link this sign-in page to. Optional — omit for standalone landing pages. | | `template_id` | enum | No | Template to use. open-house-default includes qualifying questions, open-house-minimal is name/email/phone only. Default: open-house-default. · One of: `open-house-default`, `open-house-luxury`, `open-house-minimal` | ## Example prompts - "Create an open house sign-in page for 412 Birchwood Ln with a QR code." - "Set up a minimal landing page titled Spring Buyer Seminar with just name, email, phone." ## 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. --- # landing_page_edit > Edit a landing page using natural language. Edit a landing page using natural language. Describe what you want to change (colors, text, layout, questions) and the AI will update the HTML/CSS. Same compliance guardrails as [`website_edit`](/tools/websites/website_edit) — Fair Housing, DRE, and XSS rules are enforced automatically. The edit is applied to the draft — use [`landing_page_publish`](/tools/landing-pages/landing_page_publish) to make it live. Examples: "Change the background to navy blue", "Add a question about school district preferences", "Make the welcome text larger". ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `landing_page_id` | string | Yes | UUID of the landing page to edit. Use [`landing_page_get`](/tools/landing-pages/landing_page_get) to find. | | `prompt` | string | Yes | Natural language description of the edit. Be specific. · Max length: 2000 | ## Example prompts - "On the Birchwood sign-in page, change the background to navy and enlarge the welcome text." - "Add a question about school district preferences to my open house landing page." ## Safety **Creates data + external action.** Creates a record and triggers an action in a connected external service. --- # landing_page_get > Get details of a landing page including status, shortcode URL, view count, submission count, and configuration. Get details of a landing page including status, shortcode URL, view count, submission count, and configuration. Use this to check the current state before editing or publishing. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `landing_page_id` | string | Yes | UUID of the landing page. | ## Example prompts - "How many views and sign-ups does the 412 Birchwood Ln landing page have so far?" - "Check whether my Maple Grove open house page is still in draft or live." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # landing_page_publish > Publish the current draft of a landing page to make it live. Publish the current draft of a landing page to make it live. The page will be accessible at its public URL. Only works if there is draft content to publish. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `landing_page_id` | string | Yes | UUID of the landing page to publish. | ## Example prompts - "Publish the draft sign-in page for Saturday's open house at 412 Birchwood Ln." - "Make my Spring Buyer Seminar landing page live now." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # landing_page_revert > Revert a landing page draft to the last published version. Revert a landing page draft to the last published version. Discards all unpublished changes. Only works if there is a published version to revert to. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `landing_page_id` | string | Yes | UUID of the landing page to revert. | ## Example prompts - "Throw away my draft edits and roll the Birchwood page back to the published version." - "Revert the seminar page to its last published version, but double-check with me before discarding anything." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # landing_page_submissions > Get visitor sign-in submissions for a landing page. Get visitor sign-in submissions for a landing page. Returns contact info (name, email, phone), qualifying answers, and whether each visitor completed step 1 only or both steps. Use this to review who visited an open house. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `landing_page_id` | string | Yes | UUID of the landing page. | | `limit` | number | No | Max results (default: 25). · Max: 100 · Min: 1 | | `page` | number | No | Page number (default: 1). · Min: 1 | ## Example prompts - "Who signed in at the 412 Birchwood Ln open house yesterday?" - "Pull the visitor submissions from my Maple Grove page, including their qualifying answers." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Leads > Capture, qualify, update, and convert leads into clients. Capture, qualify, update, and convert leads into clients. ## Tools (9) | Tool | Type | What it does | | --- | --- | --- | | [`leads_create`](/tools/leads/leads_create) | Creates data | Create a new lead in the CRM. | | [`leads_list`](/tools/leads/leads_list) | Read-only | Search for leads by status, source, or text. | | [`leads_update`](/tools/leads/leads_update) | Updates data | Update an existing lead's information or status. | | [`leads_get`](/tools/leads/leads_get) | Read-only | Get full details of a specific lead by ID — contact info, source, status, and timeline fields. | | [`leads_convert`](/tools/leads/leads_convert) | Irreversible | Convert a lead to a client when they become an active buyer or seller. | | [`leads_archive`](/tools/leads/leads_archive) | Updates data | Archive a lead to hide them from active views without deleting their record. | | [`leads_restore`](/tools/leads/leads_restore) | Updates data | Restore a previously archived lead back to active views. | | [`leads_delete`](/tools/leads/leads_delete) | Irreversible | Permanently delete a lead. | | [`leads_stats`](/tools/leads/leads_stats) | Read-only | Get aggregate statistics for all leads: counts by status (new/contacted/qualified/converted/lost), conversion rate, and counts by source. | --- # leads_archive > Archive a lead to hide them from active views without deleting their record. Archive a lead to hide them from active views without deleting their record. Archived leads can be restored later with [`leads_restore`](/tools/leads/leads_restore). Use this for leads that have gone cold or been disqualified but you want to keep their history. Returns the archived lead record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `lead_id` | string | Yes | UUID of the lead to archive. Use [`leads_list`](/tools/leads/leads_list) to find the ID if unknown. | ## Example prompts - "Archive the Henderson lead, they went cold after three follow-ups." - "Hide Maria's old lead from my active pipeline but keep the history." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # leads_convert > Convert a lead to a client when they become an active buyer or seller. Convert a lead to a client when they become an active buyer or seller. Use at the moment a representation agreement is signed or the lead commits to working with you. Returns the new client record linked to the original lead. > [!WARNING] > This is IRREVERSIBLE — once a lead is marked converted, the source/timeline data freezes for analytics. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `lead_id` | string | Yes | UUID of the lead to convert · Format: UUID | | `client_type` | enum | No | Type of client they are becoming · One of: `buyer`, `seller`, `both` | ## Example prompts - "The Garcias signed a buyer agreement, so convert their lead to a buyer client." - "Convert Tom Nguyen to a seller client, but confirm with me first since it is irreversible." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. ## Previous name This tool was previously published as `convert_lead_to_client`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # leads_create > Create a new lead in the CRM. Create a new lead in the CRM. Use when a new prospective buyer or seller comes in from any source. Call immediately with whatever data the user provides. Do NOT ask for missing fields — the system shows an editable draft card where the user can fill in remaining details. Returns the created lead record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `first_name` | string | Yes | First name of the lead | | `last_name` | string | Yes | Last name of the lead | | `email` | string | No | Email address | | `phone` | string | No | Phone number | | `source` | string | No | Lead source (e.g., referral, zillow, open_house, website, cold_call) | | `notes` | string | No | Notes about this lead | | `lead_type` | enum | No | Type of lead · One of: `buyer`, `seller`, `both`, `investor`, `renter` | ## Example prompts - "Add a new buyer lead: Maria Garcia, 661-555-0142, met her at the Birchwood open house." - "Create a seller lead for Tom Nguyen from Zillow, email tom.nguyen@gmail.com." ## 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. ## Previous name This tool was previously published as `create_lead`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # leads_delete > Permanently delete a lead. Permanently delete a lead. This is IRREVERSIBLE - the lead will be hidden from all views including archived. Only use for test data or duplicate records. For normal cleanup, use [`leads_archive`](/tools/leads/leads_archive) instead which is reversible. Returns confirmation of the deletion. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `lead_id` | string | Yes | UUID of the lead to delete. Use [`leads_get`](/tools/leads/leads_get) first to verify. | ## Example prompts - "Permanently delete that duplicate lead record for Maria Garcia." - "Delete the test lead I created earlier, but double-check with me before removing it permanently." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # leads_get > Get full details of a specific lead by ID — contact info, source, status, and timeline fields. Get full details of a specific lead by ID — contact info, source, status, and timeline fields. Use after [`leads_list`](/tools/leads/leads_list) when you need every field for one lead. For multiple leads, pass lead_ids instead. Returns the complete lead record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `lead_id` | string | No | UUID of a single lead to retrieve · Format: UUID | | `lead_ids` | array of strings | No | Array of lead UUIDs for batch retrieval (max 100). Use either lead_id OR lead_ids, not both. · Max items: 100 | ## Example prompts - "Pull up everything we have on the Garcia lead." - "Show me full details for these three leads I flagged this morning." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `get_lead`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # leads_list > Search for leads by status, source, or text. Search for leads by status, source, or text. Use to find lead IDs before updating or converting, or to answer questions about the lead pipeline. Returns IDs only by default for efficiency; use the fields parameter to include additional data. Response includes relatedIds.contactIds for chainable operations. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term (searches name, email, phone) | | `status` | enum | No | Filter by lead status · One of: `new`, `contacted`, `qualified`, `unqualified`, `converted`, `lost` | | `source` | string | No | Filter by lead source | | `fields` | array of enum | No | Field groups to include. Empty/omitted = IDs only. Options: basic (id, type, status), contact (name, email, phone), source (source, score), timeline (dates), full (all fields). · Values: `basic`, `contact`, `source`, `timeline`, `full` | | `limit` | string | No | Max results. Use a number (e.g. "25") or "all". "all" and any value above 200 are capped at 200 server-side. | ## Example prompts - "Show me all my qualified leads that came from open houses." - "Find leads named Garcia and include their contact info and lead score." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `search_leads`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # leads_restore > Restore a previously archived lead back to active views. Restore a previously archived lead back to active views. Reverses the effect of [`leads_archive`](/tools/leads/leads_archive). Use this when a cold lead re-engages or was archived by mistake. Returns the restored lead record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `lead_id` | string | Yes | UUID of the lead to restore. Must be currently archived. | ## Example prompts - "The Hendersons just called back, restore their archived lead." - "Unarchive Tom Nguyen's lead, I archived it by mistake last week." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # leads_stats > Get aggregate statistics for all leads: counts by status (new/contacted/qualified/converted/lost), conversion rate, and counts by source. Get aggregate statistics for all leads: counts by status (new/contacted/qualified/converted/lost), conversion rate, and counts by source. Use this for dashboard metrics and pipeline analysis. Does NOT return individual lead records - use [`leads_list`](/tools/leads/leads_list) for that. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "What's my lead conversion rate and how many new leads this month?" - "Break down my pipeline by lead status and source for me." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # leads_update > Update an existing lead's information or status. Update an existing lead's information or status. Only provided fields are updated — omitted fields remain unchanged. Common uses: advance status as the lead warms up, correct contact details, or record the source. Returns the updated lead record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `lead_id` | string | Yes | UUID of the lead to update · Format: UUID | | `first_name` | string | No | Updated first name | | `last_name` | string | No | Updated last name | | `email` | string | No | Updated email | | `phone` | string | No | Updated phone | | `status` | enum | No | Updated status · One of: `new`, `contacted`, `qualified`, `unqualified`, `converted`, `lost` | | `notes` | string | No | Notes to add | ## Example prompts - "Mark Maria Garcia's lead as contacted and note that she wants a callback Friday." - "Update Tom Nguyen's phone to 661-555-0198 and set his status to qualified." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. ## Previous name This tool was previously published as `update_lead`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # Leases > Lease record management for the property-management vertical. Lease record management for the property-management vertical. ## Tools (5) | Tool | Type | What it does | | --- | --- | --- | | [`leases_list`](/tools/leases/leases_list) | Read-only | Search the user's leases by status, lease_type, party, or free-text query. | | [`leases_get`](/tools/leases/leases_get) | Read-only | Get full details of one lease by UUID. | | [`leases_create`](/tools/leases/leases_create) | Creates data | Create a new lease agreement. | | [`leases_expiring`](/tools/leases/leases_expiring) | Read-only | List leases expiring within the next N days (default 60, max 365). | | [`leases_stats`](/tools/leases/leases_stats) | Read-only | Get aggregate stats for the user's leases: total count, breakdown by_status, active_monthly_rent_roll (sum of monthly_rent for active leases — useful for "how much recurring rental income am I managing"), and expiring_in_60_days count. | --- # leases_create > Create a new lease agreement. Create a new lease agreement. Use when a new lease is being drafted or activated outside the normal application→lease flow. For the common case of approving an application and executing the lease, use [`rental_applications_convert_to_lease`](/tools/rental-applications/rental_applications_convert_to_lease) instead — that atomically approves + creates + links. Required: lease_start, lease_end (ISO dates), monthly_rent. Defaults: status='draft', lease_type='residential'. Returns the created lease record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `listing_id` | string | No | UUID of the listing being leased · Format: UUID | | `landlord_contact_id` | string | No | UUID of the landlord contact · Format: UUID | | `renter_client_id` | string | No | UUID of the renter client (typically client_type=tenant) · Format: UUID | | `rental_application_id` | string | No | UUID of the approved application (if converted from one) · Format: UUID | | `previous_lease_id` | string | No | UUID of the prior lease (for renewals — links the chain) · Format: UUID | | `lease_start` | string | Yes | Lease start date (ISO format, YYYY-MM-DD) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `lease_end` | string | Yes | Lease end date (ISO format, YYYY-MM-DD). Must be after lease_start. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `monthly_rent` | number | Yes | Monthly rent amount · Min: 0 | | `security_deposit` | number | No | Security deposit amount · Min: 0 | | `status` | enum | No | Initial status (default: draft) · One of: `draft`, `active`, `expiring`, `renewed`, `terminated`, `expired` | | `lease_type` | enum | No | Lease type (default: residential) · One of: `residential`, `commercial`, `short_term` | | `commission_amount` | number | No | Agent commission for this lease · Min: 0 | | `notes` | string | No | Free-text notes · Max length: 10000 | ## Example prompts - "Draft a lease for the Patels at 88 Calloway Ave, 2400 monthly, July 1 to June 30." - "Create a 12-month residential lease starting August 1 at 1950 monthly with a 2000 deposit." ## 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. --- # leases_expiring > List leases expiring within the next N days (default 60, max 365). List leases expiring within the next N days (default 60, max 365). Returns active + expiring leases ordered by lease_end ascending — closest expiration first. Use this to surface renewal opportunities, proactive outreach, or renewal-vs-sale pitches. This is the primary tool for the "who needs attention this quarter" question. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `days` | number | No | Lookahead window in days (default: 60) · Max: 365 · Min: 0 | ## Example prompts - "Which of my leases expire in the next 90 days?" - "Show me upcoming lease expirations so I can pitch renewals this quarter." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # leases_get > Get full details of one lease by UUID. Get full details of one lease by UUID. Returns all lease fields including renter/landlord references, commission, renewal chain (previous_lease_id), and the rental_application_id that led to the lease. Use [`leases_list`](/tools/leases/leases_list) first if you don't have the UUID. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `lease_id` | string | Yes | UUID of the lease · Format: UUID | ## Example prompts - "Pull the full terms of the Patel lease, including deposit and renewal chain." - "What's the commission on the lease at 88 Calloway Ave?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # leases_list > Search the user's leases by status, lease_type, party, or free-text query. Search the user's leases by status, lease_type, party, or free-text query. Returns id, lease_start, lease_end, monthly_rent, status, lease_type, renter_client_id, landlord_contact_id, listing_id. Use status='expiring' or the dedicated [`leases_expiring`](/tools/leases/leases_expiring) tool to find leases ending soon — the dedicated view is more useful when looking for renewal opportunities. Pagination: total_count + has_more + offset + limit. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Free-text search (reserved — not currently indexed; use specific filters instead) | | `status` | enum | No | Filter by lease status. active=currently occupied, expiring=within renewal window, renewed=has successor lease, terminated=ended early, expired=passed lease_end with no renewal · One of: `draft`, `active`, `expiring`, `renewed`, `terminated`, `expired` | | `lease_type` | enum | No | Filter by lease type · One of: `residential`, `commercial`, `short_term` | | `renter_client_id` | string | No | Filter to leases for a specific renter (client). Use [`clients_list`](/tools/clients/clients_list) with client_type=tenant to find tenants first. · Format: UUID | | `landlord_contact_id` | string | No | Filter to leases for a specific landlord (contact). Use [`contacts_list`](/tools/contacts/contacts_list) with leasing_role=landlord to find landlords first. · Format: UUID | | `listing_id` | string | No | Filter to leases for a specific listing · Format: UUID | | `limit` | number | No | Maximum results (default: 25) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "List all my active residential leases with their monthly rent." - "Show every lease tied to the 88 Calloway Ave listing." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # leases_stats > Get aggregate stats for the user's leases: total count, breakdown by_status, active_monthly_rent_roll (sum of monthly_rent for active leases — useful for "how much recurring rental income am I managing"), and expiring_in_60_days count. Get aggregate stats for the user's leases: total count, breakdown by_status, active_monthly_rent_roll (sum of monthly_rent for active leases — useful for "how much recurring rental income am I managing"), and expiring_in_60_days count. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "How much monthly rent roll am I managing across active leases?" - "Give me lease counts by status and how many expire within 60 days." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Listings > Your property inventory — create, search, update, and manage listings. Your property inventory — create, search, update, and manage listings. ## Tools (9) | Tool | Type | What it does | | --- | --- | --- | | [`listings_list`](/tools/listings/listings_list) | Read-only | Search for property listings by address, MLS number, status, or price range. | | [`listings_get`](/tools/listings/listings_get) | Read-only | Get full details of one or more listings by UUID. | | [`listings_create`](/tools/listings/listings_create) | Creates data | Create a new property listing. | | [`listings_update`](/tools/listings/listings_update) | Updates data | Update an existing listing's information or status. | | [`listings_stats`](/tools/listings/listings_stats) | Read-only | Get aggregate statistics for all listings: counts by status (active/pending/sold/expired), total active listings value, and average days on market. | | [`listings_expiring`](/tools/listings/listings_expiring) | Read-only | Get listings approaching or past their expiration date. | | [`listings_archive`](/tools/listings/listings_archive) | Updates data | Archive a listing to hide it from active views without deleting it. | | [`listings_restore`](/tools/listings/listings_restore) | Updates data | Restore a previously archived listing back to active views. | | [`listings_delete`](/tools/listings/listings_delete) | Irreversible | Permanently delete a listing. | --- # listings_archive > Archive a listing to hide it from active views without deleting it. Archive a listing to hide it from active views without deleting it. Archived listings can be restored later with [`listings_restore`](/tools/listings/listings_restore). Use this for expired or sold listings you want to declutter from your dashboard. Returns the archived listing record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `listing_id` | string | Yes | UUID of the listing to archive. Use [`listings_list`](/tools/listings/listings_list) to find the ID if unknown. · Format: UUID | ## Example prompts - "Archive the sold listing at 901 Marsh Creek Dr to declutter my dashboard." - "Hide that expired Birchwood listing from my active views, keep the record." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # listings_create > Create a new property listing. Create a new property listing. Call immediately with whatever data the user provides. Do NOT ask for missing fields — the system shows an editable draft card where the user can fill in remaining details. WORKFLOW: 1) Use [`lookup_address`](/tools/utility/lookup_address) first to get verified address data with coordinates 2) Create the listing with property details 3) Optionally schedule open houses with [`create_open_house`](/tools/deadline/create_open_house). Returns the created listing with ID. Required fields: property_address and list_price. May trigger notifications if integrations are configured. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `property_address` | string | Yes | Full property address (required). Use [`lookup_address`](/tools/utility/lookup_address) first for verified data. | | `display_address` | string | No | Display address if different (e.g., "123 Main St, Unit 4B"). | | `city` | string | No | City. | | `state` | string | No | State abbreviation (e.g., CA). | | `zip_code` | string | No | ZIP code. | | `county` | string | No | County name. | | `latitude` | number | No | Latitude coordinate (from [`lookup_address`](/tools/utility/lookup_address)). | | `longitude` | number | No | Longitude coordinate (from [`lookup_address`](/tools/utility/lookup_address)). | | `list_price` | number | Yes | Listing price in dollars (required). · Min: 0 | | `mls_number` | string | No | MLS number (RESO ListingId). | | `bedrooms` | number | No | Number of bedrooms. · Min: 0 | | `bathrooms` | number | No | Number of bathrooms (can be decimal for half baths). · Min: 0 | | `square_feet` | number | No | Square footage (RESO LivingArea). · Min: 0 | | `lot_size` | number | No | Lot size in square feet. | | `year_built` | number | No | Year built. | | `garage_spaces` | number | No | Number of garage spaces. | | `stories` | number | No | Number of stories. | | `property_type` | enum | No | Type of property (RESO PropertyType). · One of: `single_family`, `condo`, `townhouse`, `multi_family`, `land`, `commercial` | | `property_sub_type` | string | No | RESO PropertySubType (e.g., Attached, Detached). | | `listing_date` | string | No | Date listing goes active on MLS. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `expiration_date` | string | No | Listing agreement expiration date — important for tracking. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `listing_status` | enum | No | Initial listing status. · One of: `active`, `pending`, `coming_soon` | | `description` | string | No | Property description (also sets public_remarks). | | `public_remarks` | string | No | RESO PublicRemarks (MLS description). | | `showing_instructions` | string | No | RESO ShowingInstructions. | | `virtual_tour_link` | string | No | Virtual tour URL (branded). | | `list_agent_mls_id` | string | No | RESO ListAgentMlsId. | | `list_agent_full_name` | string | No | RESO ListAgentFullName. | | `list_office_name` | string | No | RESO ListOfficeName. | ## Example prompts - "Create a listing for 412 Birchwood Ln at 489,000, 4 bed 3 bath, 2,150 square feet." - "List the Garcias' condo at 901 Marsh Creek Dr for 315,000 as coming soon." ## 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. ## Previous name This tool was previously published as `create_listing`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # listings_delete > Permanently delete a listing. Permanently delete a listing. This is IRREVERSIBLE — the listing will be hidden from all views, including archived. Only use for test data or duplicate records. For normal cleanup, use [`listings_archive`](/tools/listings/listings_archive) instead which is reversible. Returns confirmation of the deletion. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `listing_id` | string | Yes | UUID of the listing to delete. Use [`listings_get`](/tools/listings/listings_get) first to verify. · Format: UUID | ## Example prompts - "Permanently delete the duplicate listing record for 412 Birchwood Ln." - "Remove that test listing for good, but double-check with me before deleting it permanently." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # listings_expiring > Get listings approaching or past their expiration date. Get listings approaching or past their expiration date. PROSPECTING TOOL: Expiring listings are opportunities to acquire new business — contact sellers whose listings are about to expire. Returns listings sorted by expiration date. Use days_until_expiration to set the lookback window. include_expired=true also shows recently expired listings (within expired_within_days). Default shows active listings expiring in next 30 days plus expired within 14 days. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `days_until_expiration` | number | No | Show listings expiring within X days (default: 30). · Min: 1 | | `include_expired` | boolean | No | Include recently expired listings (default: true). | | `expired_within_days` | number | No | If including expired, how many days back to look (default: 14). · Min: 1 | ## Example prompts - "Which listings in my pipeline expire within the next 30 days?" - "Show recently expired listings so I can call those sellers about relisting." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # listings_get > Get full details of one or more listings by UUID. Get full details of one or more listings by UUID. Supports BOTH single and batch modes: pass listing_id for one listing, or listing_ids array for efficient multi-fetch (up to 100 IDs). Single mode returns all listing fields including full description and MLS data. Batch mode returns array of listings with count and not_found list. If you don't have the UUID, use [`listings_list`](/tools/listings/listings_list) first. For matching listings to buyers, use [`match_buyers_to_listings`](/tools/reporting/match_buyers_to_listings). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `listing_id` | string | No | UUID of a single listing. Use [`listings_list`](/tools/listings/listings_list) to find IDs. · Format: UUID | | `listing_ids` | array of strings | No | Array of listing UUIDs for batch retrieval (max 100). More efficient than multiple single calls. · Max items: 100 | ## Example prompts - "Pull the full MLS details for the 412 Birchwood Ln listing." - "Fetch complete details for these five listing IDs in one batch." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `get_listing`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # listings_list > Search for property listings by address, MLS number, status, or price range. Search for property listings by address, MLS number, status, or price range. Returns pagination info (total_count, has_more, offset, limit) for batch operations. Results include: id, property_address, city, state, zip_code, list_price, listing_status, property_type, bedrooms, bathrooms, square_feet, created_at. Filter by status to find active listings vs sold/expired. Use min_price/max_price to match buyer budgets. For a specific listing by ID, use [`listings_get`](/tools/listings/listings_get) instead. For aggregate stats, use [`listings_stats`](/tools/listings/listings_stats). Default limit is 20 when not provided; if the default is used and more results exist, the response includes truncated: true and total: N so you can rerun with a higher limit. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term — matches against property_address, city, and mls_number (case-insensitive partial match). | | `status` | enum | No | Filter by listing status. active=on market, pending=under contract, sold=closed, expired=listing ended, coming_soon=pre-market (default: all). · One of: `all`, `active`, `pending`, `sold`, `expired`, `cancelled`, `coming_soon` | | `min_price` | number | No | Minimum listing price in dollars. Use with max_price for buyer matching. · Min: 0 | | `max_price` | number | No | Maximum listing price in dollars. Use with min_price for buyer matching. · Min: 0 | | `property_type` | enum | No | Filter by property type. · One of: `single_family`, `condo`, `townhouse`, `multi_family`, `land`, `commercial` | | `limit` | number | No | Maximum results (default: 20, max: 500). When omitted and more results exist, response includes truncated: true + total: N. · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0). · Min: 0 | ## Example prompts - "Find active single family listings between 400k and 550k for the Garcias." - "Search my listings for anything on Birchwood Ln in Bakersfield." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `search_listings`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # listings_restore > Restore a previously archived listing back to active views. Restore a previously archived listing back to active views. Reverses the effect of [`listings_archive`](/tools/listings/listings_archive). Use this when a listing needs to be reactivated or was archived by mistake. Returns the restored listing record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `listing_id` | string | Yes | UUID of the listing to restore. Must be currently archived. · Format: UUID | ## Example prompts - "Restore the archived Marsh Creek listing, the sellers want to relist." - "Unarchive 412 Birchwood Ln, I archived it by accident." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # listings_stats > Get aggregate statistics for all listings: counts by status (active/pending/sold/expired), total active listings value, and average days on market. Get aggregate statistics for all listings: counts by status (active/pending/sold/expired), total active listings value, and average days on market. Use this for dashboard metrics and pipeline overview. Does NOT return individual listing records — use [`listings_list`](/tools/listings/listings_list) for that. Returns statusCounts array and activeListingsValue total. For specific listings, use [`listings_list`](/tools/listings/listings_list) with filters. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "What's my total active listings value and average days on market?" - "Give me a count of my listings by status for the dashboard." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. ## Previous name This tool was previously published as `get_listings_summary`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # listings_update > Update an existing listing's information or status. Update an existing listing's information or status. Only provided fields are updated — omitted fields remain unchanged. Common uses: price reduction (update list_price), status change (active→pending→sold), address correction, extend expiration date. Status transitions: active → pending (offer accepted) → sold (closed) or expired/cancelled (listing ended). Returns the updated listing record. If the listing_id is not found, the error suggests using [`listings_list`](/tools/listings/listings_list). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `listing_id` | string | Yes | UUID of the listing to update (required). Use [`listings_list`](/tools/listings/listings_list) to find the ID if unknown. · Format: UUID | | `property_address` | string | No | Updated street address. | | `display_address` | string | No | Updated display address (e.g., with unit number). | | `city` | string | No | Updated city name. | | `state` | string | No | Updated state abbreviation. | | `zip_code` | string | No | Updated ZIP code. | | `county` | string | No | Updated county name. | | `latitude` | number | No | Updated latitude coordinate. | | `longitude` | number | No | Updated longitude coordinate. | | `list_price` | number | No | Updated listing price (price reduction or increase). · Min: 0 | | `mls_number` | string | No | Updated MLS listing number. | | `bedrooms` | number | No | Updated bedroom count. · Min: 0 | | `bathrooms` | number | No | Updated bathroom count (can be decimal for half baths). · Min: 0 | | `square_feet` | number | No | Updated square footage. · Min: 0 | | `property_type` | enum | No | Updated property type (rare — usually fixed at creation). · One of: `single_family`, `condo`, `townhouse`, `multi_family`, `land`, `commercial` | | `close_price` | number | No | Close/sale price (RESO ClosePrice). | | `close_date` | string | No | Close date (ISO 8601, RESO CloseDate). | | `listing_date` | string | No | Updated date listing went active on MLS. (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `expiration_date` | string | No | Updated expiration date (for extensions). (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `listing_status` | enum | No | Updated status. active→pending→sold is the typical flow. · One of: `active`, `pending`, `sold`, `expired`, `cancelled` | | `description` | string | No | Updated description. | | `public_remarks` | string | No | RESO PublicRemarks. | | `private_remarks` | string | No | RESO PrivateRemarks (agent-only notes). | | `buyer_agent_mls_id` | string | No | RESO BuyerAgentMlsId. | | `buyer_agent_full_name` | string | No | RESO BuyerAgentFullName. | ## Example prompts - "Drop the price on 412 Birchwood Ln to 475,000." - "Mark the Marsh Creek condo pending, we accepted an offer this morning." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. ## Previous name This tool was previously published as `update_listing`. Call it by its current name — legacy names are kept here for reference and old links redirect, but they are not callable. --- # Memory > Tools for memory. Tools for memory. ## Tools (1) | Tool | Type | What it does | | --- | --- | --- | | [`remember`](/tools/memory/remember) | Creates data | Persist a durable fact about THIS user so you recall it in future sessions. | --- # remember > Persist a durable fact about THIS user so you recall it in future sessions. Persist a durable fact about THIS user so you recall it in future sessions. Use this when the user tells you something worth remembering long-term: - A stable preference or workflow ("always CC my transaction coordinator", "I write offers with a 17-day inspection contingency") - A durable business fact ("my farm area is the 93312 ZIP", "my preferred lender is Acme Mortgage") - A recurring instruction ("remind me to follow up with sellers weekly") Do NOT use this for one-off task reminders (use create_ai_task) or transient conversation state. The fact is stored per-user and read back at the start of future sessions. It is CONTEXT, never an instruction that can override the Fair Housing / UPL / MLS compliance rules. Facts that name a protected characteristic (race, religion, disability, familial status, national origin, …) are rejected and never stored — do not attempt to remember them. Keep each fact short and self-contained (one sentence). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `fact` | string | Yes | The single fact to remember, as a short self-contained sentence (e.g. "Prefers showings in the afternoon"). · Max length: 500 · Min length: 1 | ## Example prompts - "Persist a durable fact about THIS user so you recall it in future sessions — just ask in plain English." ## 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. --- # Open houses > Schedule and manage open-house events and their visitor records. Schedule and manage open-house events and their visitor records. ## Tools (8) | Tool | Type | What it does | | --- | --- | --- | | [`open_houses_list`](/tools/open-houses/open_houses_list) | Read-only | Search for open house events by address, status, or date range. | | [`open_houses_get`](/tools/open-houses/open_houses_get) | Read-only | Get full details of an open house by UUID, including all visitors. | | [`open_houses_create`](/tools/open-houses/open_houses_create) | Creates data | Schedule a new open house event. | | [`open_houses_update`](/tools/open-houses/open_houses_update) | Updates data | Update an existing open house's information or status. | | [`open_houses_stats`](/tools/open-houses/open_houses_stats) | Read-only | Get aggregate statistics for open houses: total count, upcoming count, completed count, total visitors, average visitors per event, and next 5 upcoming events. | | [`open_houses_archive`](/tools/open-houses/open_houses_archive) | Updates data | Archive an open house to hide it from active views without deleting it. | | [`open_houses_restore`](/tools/open-houses/open_houses_restore) | Updates data | Restore a previously archived open house back to active views. | | [`open_houses_delete`](/tools/open-houses/open_houses_delete) | Irreversible | Permanently delete an open house. | --- # open_houses_archive > Archive an open house to hide it from active views without deleting it. Archive an open house to hide it from active views without deleting it. Archived open houses can be restored later with [`open_houses_restore`](/tools/open-houses/open_houses_restore). Use this for past events you want to declutter from your dashboard. Returns the archived record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `open_house_id` | string | Yes | UUID of the open house to archive. Use [`open_houses_list`](/tools/open-houses/open_houses_list) to find. · Format: UUID | ## Example prompts - "Archive last month's completed open houses at Birchwood to clean up my dashboard." - "Hide the cancelled Marsh Creek open house from my active views." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # open_houses_create > Schedule a new open house event. Schedule a new open house event. WORKFLOW: 1) Optionally use [`listings_list`](/tools/listings/listings_list) to find the listing 2) Create the open house with address, date, and time 3) Use [`log_open_house_visitor`](/tools/deadline/log_open_house_visitor) to log visitors during the event. Returns the created open house with ID. Required fields: address, date, start_time, end_time. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `address` | string | Yes | Property address for the open house (required) | | `listing_id` | string | No | UUID of the associated listing (optional). Use [`listings_list`](/tools/listings/listings_list) to find. · Format: UUID | | `list_price` | number | No | Property list price in dollars · Min: 0 | | `date` | string | Yes | Date of the open house (required) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `start_time` | string | Yes | Start time in HH:MM format (required), e.g. "13:00" | | `end_time` | string | Yes | End time in HH:MM format (required), e.g. "16:00" | | `status` | enum | No | Initial status (default: scheduled) · One of: `scheduled`, `in_progress`, `completed`, `cancelled` | | `notes` | string | No | Notes or special instructions for the open house | ## Example prompts - "Schedule an open house at 412 Birchwood Ln this Saturday from 1 to 4." - "Set up a Sunday open house for the Marsh Creek condo, noon to three." ## 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. --- # open_houses_delete > Permanently delete an open house. Permanently delete an open house. This is IRREVERSIBLE - the open house will be hidden from all views, including archived. The open house must be archived first. For normal cleanup, use [`open_houses_archive`](/tools/open-houses/open_houses_archive) instead which is reversible. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `open_house_id` | string | Yes | UUID of the open house to delete. Must be archived first. Use [`open_houses_get`](/tools/open-houses/open_houses_get) to verify. · Format: UUID | ## Example prompts - "Permanently delete that duplicate open house entry for 412 Birchwood Ln." - "Delete the archived test open house, but double-check with me before removing it permanently." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # open_houses_get > Get full details of an open house by UUID, including all visitors. Get full details of an open house by UUID, including all visitors. Returns address, date/time, status, notes, visitor_count, and full visitor list with contact info and interest level. If you don't have the UUID, use [`open_houses_list`](/tools/open-houses/open_houses_list) first. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `open_house_id` | string | Yes | UUID of the open house. Use [`open_houses_list`](/tools/open-houses/open_houses_list) to find IDs. · Format: UUID | ## Example prompts - "Show me the sign-in list from Sunday's open house at 412 Birchwood Ln." - "Pull the details and visitors for that Birchwood open house, including interest levels." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # open_houses_list > Search for open house events by address, status, or date range. Search for open house events by address, status, or date range. Returns pagination info (total_count, has_more, offset, limit). Results include: id, address, list_price, date, start_time, end_time, status, visitor_count, notes, created_at. Filter by status (scheduled/in_progress/completed/cancelled) or date range. For a specific open house by ID, use [`open_houses_get`](/tools/open-houses/open_houses_get) instead. For aggregate stats, use [`open_houses_stats`](/tools/open-houses/open_houses_stats). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term - matches against address (case-insensitive partial match) | | `status` | enum | No | Filter by status. scheduled=upcoming, in_progress=happening now, completed=past, cancelled=cancelled (default: all) · One of: `all`, `scheduled`, `in_progress`, `completed`, `cancelled` | | `date_from` | string | No | Show open houses on or after this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `date_to` | string | No | Show open houses on or before this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `archived` | boolean | No | Include archived open houses (default: false) | | `limit` | number | No | Maximum results (default: 50, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "What open houses do I have scheduled for this weekend?" - "List completed open houses at 412 Birchwood Ln with their visitor counts." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # open_houses_restore > Restore a previously archived open house back to active views. Restore a previously archived open house back to active views. Reverses the effect of [`open_houses_archive`](/tools/open-houses/open_houses_archive). Returns the restored record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `open_house_id` | string | Yes | UUID of the open house to restore. Must be currently archived. · Format: UUID | ## Example prompts - "Restore the archived Birchwood open house, I still need its visitor list." - "Unarchive Sunday's open house event, it was archived by mistake." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # open_houses_stats > Get aggregate statistics for open houses: total count, upcoming count, completed count, total visitors, average visitors per event, and next 5 upcoming events. Get aggregate statistics for open houses: total count, upcoming count, completed count, total visitors, average visitors per event, and next 5 upcoming events. Use this for dashboard metrics. Does NOT return individual records - use [`open_houses_list`](/tools/open-houses/open_houses_list) for that. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `period` | enum | No | Time period for stats (default: 1_month) · One of: `1_day`, `1_week`, `1_month`, `3_months`, `1_year`, `ytd`, `all` | ## Example prompts - "How many visitors did my open houses average over the last three months?" - "Give me open house metrics for the year plus my next five upcoming events." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # open_houses_update > Update an existing open house's information or status. Update an existing open house's information or status. Only provided fields are updated - omitted fields remain unchanged. Common uses: reschedule (update date/times), status change (scheduled→in_progress→completed), add notes. Returns the updated open house record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `open_house_id` | string | Yes | UUID of the open house to update (required). Use [`open_houses_list`](/tools/open-houses/open_houses_list) to find. · Format: UUID | | `address` | string | No | Updated property address | | `listing_id` | string | No | Updated listing ID · Format: UUID | | `list_price` | number | No | Updated list price · Min: 0 | | `date` | string | No | Updated date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `start_time` | string | No | Updated start time in HH:MM format | | `end_time` | string | No | Updated end time in HH:MM format | | `status` | enum | No | Updated status · One of: `scheduled`, `in_progress`, `completed`, `cancelled` | | `notes` | string | No | Updated notes | ## Example prompts - "Move Saturday's Birchwood open house to 2 until 5 instead." - "Mark the Marsh Creek open house completed and note we had heavy foot traffic." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # Partners (vendor pipeline) > Manage vendor-partner relationships — create, update, stats, and lifecycle operations. Manage vendor-partner relationships — create, update, stats, and lifecycle operations. ## Tools (8) | Tool | Type | What it does | | --- | --- | --- | | [`partners_list`](/tools/partners/partners_list) | Read-only | Search for vendor partners by name, status, vendor type, or tier. | | [`partners_get`](/tools/partners/partners_get) | Read-only | Get full details of a vendor partner by UUID, including contact info, vendor type, tier, partner_since date, notes, tags, and relationship history. | | [`partners_create`](/tools/partners/partners_create) | Creates data | Create a new vendor partner to track an established vendor relationship. | | [`partners_update`](/tools/partners/partners_update) | Updates data | Update an existing vendor partner's information or status. | | [`partners_stats`](/tools/partners/partners_stats) | Read-only | Get aggregate statistics for vendor partners: total count, counts by status, counts by tier, counts by vendor type, active vs churned ratio. | | [`partners_archive`](/tools/partners/partners_archive) | Updates data | Archive a vendor partner to hide it from active views without deleting it. | | [`partners_restore`](/tools/partners/partners_restore) | Updates data | Restore a previously archived vendor partner back to active views. | | [`partners_delete`](/tools/partners/partners_delete) | Irreversible | Permanently delete a vendor partner. | --- # partners_archive > Archive a vendor partner to hide it from active views without deleting it. Archive a vendor partner to hide it from active views without deleting it. Archived partners can be restored later with [`partners_restore`](/tools/partners/partners_restore). Use this for churned or paused partners you want to declutter from your dashboard. Returns the archived record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `partner_id` | string | Yes | UUID of the partner to archive. Use [`partners_list`](/tools/partners/partners_list) to find. · Format: UUID | ## Example prompts - "Archive the churned contractor partner record for Reyes Construction." - "Hide Lena Ortiz's paused partnership from my active roster without losing the history." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # partners_create > Create a new vendor partner to track an established vendor relationship. Create a new vendor partner to track an established vendor relationship. WORKFLOW: 1) Optionally use [`contacts_list`](/tools/contacts/contacts_list) to find the contact 2) Create the partner with vendor_type and relationship details. Returns the created partner with ID and display_id. Tier defaults to 'standard' if not specified. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_id` | string | No | UUID of an existing contact for this partner. Use [`contacts_list`](/tools/contacts/contacts_list) to find. · Format: UUID | | `vendor_type` | string | Yes | Type of vendor (e.g. lender, inspector, escrow_officer, title_rep, appraiser, contractor, photographer) | | `title` | string | No | Title or name for this partner record | | `tier` | enum | No | Partner tier level (default: standard) · One of: `standard`, `preferred`, `vip` | | `partner_since` | string | No | Date the partnership began (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `notes` | string | No | Additional notes about the partner relationship | | `tags` | array of strings | No | Tags for categorization (e.g. ["reliable", "fast-turnaround", "bilingual"]) | ## Example prompts - "Add Marcus Webb at Summit Lending as a new preferred lender partner since March." - "Create a photographer partner record for Lena Ortiz, tag her fast-turnaround and bilingual." ## 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. --- # partners_delete > Permanently delete a vendor partner. Permanently delete a vendor partner. This is IRREVERSIBLE - the partner will be hidden from all views including archived. The partner must be archived first. For normal cleanup, use [`partners_archive`](/tools/partners/partners_archive) instead, which is reversible. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `partner_id` | string | Yes | UUID of the partner to delete. Must be archived first. Use [`partners_get`](/tools/partners/partners_get) to verify. · Format: UUID | ## Example prompts - "Permanently delete the duplicate partner record for Dana Whitfield." - "Delete that archived test partner for good, but double-check with me before removing it." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # partners_get > Get full details of a vendor partner by UUID, including contact info, vendor type, tier, partner_since date, notes, tags, and relationship history. Get full details of a vendor partner by UUID, including contact info, vendor type, tier, partner_since date, notes, tags, and relationship history. Returns all fields. If you don't have the UUID, use [`partners_list`](/tools/partners/partners_list) first. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `partner_id` | string | Yes | UUID of the partner. Use [`partners_list`](/tools/partners/partners_list) to find IDs. · Format: UUID | ## Example prompts - "Pull up the full relationship history for my title rep Dana Whitfield." - "What tier is Marcus Webb in and how long has he been a partner?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # partners_list > Search for vendor partners by name, status, vendor type, or tier. Search for vendor partners by name, status, vendor type, or tier. Returns pagination info (total_count, has_more, offset, limit). Results include: id, display_id, title, vendor_type, status, tier, partner_since, care_status, contact info, created_at. Filter by status (onboarding/active/preferred/paused/churned), tier (standard/preferred/vip), vendor_type, or care_status. For a specific partner by ID, use [`partners_get`](/tools/partners/partners_get) instead. For aggregate stats, use [`partners_stats`](/tools/partners/partners_stats). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term - matches against title, notes (case-insensitive partial match) | | `status` | enum | No | Filter by status. onboarding=setting up, active=regular partner, preferred=top partner, paused=temporarily inactive, churned=relationship ended (default: all) · One of: `all`, `onboarding`, `active`, `preferred`, `paused`, `churned` | | `tier` | enum | No | Filter by partner tier (default: all) · One of: `all`, `standard`, `preferred`, `vip` | | `vendor_type` | string | No | Filter by vendor type (e.g. lender, inspector, escrow_officer, title_rep, appraiser, contractor, photographer) | | `care_status` | enum | No | Filter by care status (default: all) · One of: `all`, `no_status`, `cared`, `needs_care`, `didnt_care` | | `date_from` | string | No | Show partners created on or after this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `date_to` | string | No | Show partners created on or before this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `archived` | boolean | No | Include archived partners (default: false) | | `limit` | number | No | Maximum results (default: 50, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "Show me all my preferred tier lender partners." - "List active inspector partners flagged as needing care this month." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # partners_restore > Restore a previously archived vendor partner back to active views. Restore a previously archived vendor partner back to active views. Reverses the effect of [`partners_archive`](/tools/partners/partners_archive). Returns the restored record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `partner_id` | string | Yes | UUID of the partner to restore. Must be currently archived. · Format: UUID | ## Example prompts - "Restore the archived partner record for Reyes Construction, they're back on board." - "Unarchive Marcus Webb's partner record, I shelved it by mistake." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # partners_stats > Get aggregate statistics for vendor partners: total count, counts by status, counts by tier, counts by vendor type, active vs churned ratio. Get aggregate statistics for vendor partners: total count, counts by status, counts by tier, counts by vendor type, active vs churned ratio. Use this for dashboard metrics. Does NOT return individual records - use [`partners_list`](/tools/partners/partners_list) for that. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `period` | enum | No | Time period for stats (default: 1_month) · One of: `1_day`, `1_week`, `1_month`, `3_months`, `1_year`, `ytd`, `all` | ## Example prompts - "How many active versus churned partners do I have this year?" - "Break down my partner roster by vendor type and tier." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # partners_update > Update an existing vendor partner's information or status. ```text Update an existing vendor partner's information or status. Only provided fields are updated - omitted fields remain unchanged. Common uses: status change (onboarding->active->preferred), tier upgrade, update notes. Returns the updated partner record. ``` ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `partner_id` | string | Yes | UUID of the partner to update (required). Use [`partners_list`](/tools/partners/partners_list) to find. · Format: UUID | | `contact_id` | string | No | Updated contact ID. Use [`contacts_list`](/tools/contacts/contacts_list) to find. · Format: UUID | | `vendor_type` | string | No | Updated vendor type | | `title` | string | No | Updated title | | `status` | enum | No | Updated status · One of: `onboarding`, `active`, `preferred`, `paused`, `churned` | | `tier` | enum | No | Updated partner tier · One of: `standard`, `preferred`, `vip` | | `partner_since` | string | No | Updated partnership start date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `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 - "Bump Dana Whitfield to VIP tier, she closed three escrows with us this quarter." - "Mark Marcus Webb as needs care and note we haven't touched base since April." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # Pipelines > Config-driven pipeline engine: overview, record management, stage moves, and batch stage operations. Config-driven pipeline engine: overview, record management, stage moves, and batch stage operations. ## Tools (15) | Tool | Type | What it does | | --- | --- | --- | | [`pipeline_overview`](/tools/pipelines/pipeline_overview) | Read-only | Get pipeline counts grouped by industry vertical for the current user. | | [`pipeline_types_list`](/tools/pipelines/pipeline_types_list) | Read-only | List available pipeline types for the current user based on their role. | | [`pipeline_stages_list`](/tools/pipelines/pipeline_stages_list) | Read-only | Get the ordered stages (funnel) for a specific pipeline type. | | [`pipeline_records_create`](/tools/pipelines/pipeline_records_create) | Creates data | Create a new pipeline record. | | [`pipeline_records_list`](/tools/pipelines/pipeline_records_list) | Read-only | List pipeline records with filtering. | | [`pipeline_records_get`](/tools/pipelines/pipeline_records_get) | Read-only | Get a single pipeline record by ID with full details including contact info, current stage, pipeline type, and stage-specific fields. | | [`pipeline_records_update`](/tools/pipelines/pipeline_records_update) | Updates data | Update a pipeline record's fields — title, source, estimated_ltv, priority, notes, tags, record_data, and more. | | [`pipeline_records_move_stage`](/tools/pipelines/pipeline_records_move_stage) | Updates data | Move a pipeline record to a new stage. | | [`pipeline_records_delete`](/tools/pipelines/pipeline_records_delete) | Irreversible | Delete a pipeline record. | | [`pipeline_records_archive`](/tools/pipelines/pipeline_records_archive) | Updates data | Archive a pipeline record to hide it from default views without deleting it. | | [`pipeline_records_restore`](/tools/pipelines/pipeline_records_restore) | Updates data | Restore an archived pipeline record back to active status. | | [`pipeline_records_stats`](/tools/pipelines/pipeline_records_stats) | Read-only | Get pipeline statistics: funnel counts per stage, total LTV, total revenue, conversion rate, records needing follow-up, and records expiring soon. | | [`pipeline_record_activities`](/tools/pipelines/pipeline_record_activities) | Read-only | Get the activity history for a pipeline record — stage changes, notes, calls, meetings, and other logged activities in reverse chronological order. | | [`pipeline_record_log_activity`](/tools/pipelines/pipeline_record_log_activity) | Logs activity | Log an activity on a pipeline record. | | [`pipeline_records_batch_stage`](/tools/pipelines/pipeline_records_batch_stage) | Bulk changes | Move multiple pipeline records to the same stage. | --- # pipeline_overview > Get pipeline counts grouped by industry vertical for the current user. Get pipeline counts grouped by industry vertical for the current user. Returns lead, appointment, client, and stage-4 counts per vertical. Useful for understanding pipeline volume across different business verticals. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "How is my pipeline volume looking across each industry vertical right now?" - "Give me a quick count of leads, appointments, and clients per vertical." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # pipeline_record_activities > Get the activity history for a pipeline record — stage changes, notes, calls, meetings, and other logged activities in reverse chronological order. Get the activity history for a pipeline record — stage changes, notes, calls, meetings, and other logged activities in reverse chronological order. Use to review what has happened on a record before the next touch. Returns the activity list. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `record_id` | string | Yes | Pipeline record UUID · Format: UUID | | `limit` | integer | No | Max activities to return (default: 20) · Max: 100 · Min: 1 | ## Example prompts - "Show me the full activity history on the Smith Brokerage record." - "What stage changes and calls have been logged for Keystone Realty lately?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # pipeline_record_log_activity > Log an activity on a pipeline record. Log an activity on a pipeline record. Use for notes, calls, emails, meetings, demos, or tasks. Creates a timestamped entry in the record's activity history. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `record_id` | string | Yes | Pipeline record UUID · Format: UUID | | `activity_type` | enum | Yes | Type of activity · One of: `note`, `call`, `email`, `meeting`, `demo`, `task`, `other` | | `subject` | string | No | Activity subject/title | | `body` | string | No | Activity details/notes | | `details` | object | No | Structured activity data | ## Example prompts - "Log a call on the Smith Brokerage record, we discussed pricing for 15 seats." - "Add a note to the Keystone Realty record about their demo scheduled Friday." ## Safety **Logs activity.** Adds an activity log entry. Your existing records are not changed. --- # pipeline_records_archive > Archive a pipeline record to hide it from default views without deleting it. Archive a pipeline record to hide it from default views without deleting it. Use for stale or inactive records you want out of the way — restore later with [`pipeline_records_restore`](/tools/pipelines/pipeline_records_restore). Returns the archived record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | Yes | Pipeline record UUID · Format: UUID | ## Example prompts - "Archive the Hillcrest Lending record, that deal has gone completely cold." - "Hide the Smith Brokerage record from my active pipeline without deleting it." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # pipeline_records_batch_stage > Move multiple pipeline records to the same stage. Move multiple pipeline records to the same stage. All records must belong to the same pipeline type. Logs individual stage transitions for each record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `ids` | array of strings | Yes | Array of pipeline record UUIDs · Max items: 100 | | `stage_key` | string | Yes | Target stage key | | `notes` | string | No | Notes about the batch stage change | ## Example prompts - "Move all five of my trial accounts to the paid stage at once." - "Batch move these stalled demo records back to lead, but confirm the list with me first." ## Safety **Bulk changes.** Changes many records in one call. Review the scope carefully before confirming — bulk changes are treated as destructive because of their blast radius. --- # pipeline_records_create > Create a new pipeline record. Create a new pipeline record. Provide contact_id for an existing contact, OR first_name + last_name (+ optional email/phone) to auto-create a contact. The record starts at the default (first) stage. Returns the created record with ID for subsequent operations. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `pipeline_type_id` | string | Yes | Pipeline type UUID (use [`pipeline_types_list`](/tools/pipelines/pipeline_types_list) to find) · Format: UUID | | `contact_id` | string | No | Existing contact UUID (optional if providing name/email) · Format: UUID | | `first_name` | string | No | First name for auto-creating a contact | | `last_name` | string | No | Last name for auto-creating a contact | | `email` | string | No | Email address · Format: Email address | | `phone` | string | No | Phone number | | `company` | string | No | Company name | | `title` | string | No | Record title (e.g., "Smith Brokerage — 15 seats") | | `source` | string | No | Lead source (referral, website, ad, cold_call, etc.) | | `estimated_ltv` | number | No | Estimated lifetime value in dollars | | `expected_close_date` | string | No | Expected conversion date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `priority` | enum | No | Priority level · One of: `low`, `medium`, `high`, `urgent` | | `notes` | string | No | Notes about this record | | `record_data` | object | No | Stage-specific fields as key-value pairs | ## Example prompts - "Add Smith Brokerage as a new pipeline record with an estimated 18000 dollar lifetime value." - "Create a pipeline record for Dana Whitfield at Keystone Realty, high priority, source networking event." ## 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. --- # pipeline_records_delete > Delete a pipeline record. Delete a pipeline record. Use for records created by mistake or test data — for records you may need again, prefer [`pipeline_records_archive`](/tools/pipelines/pipeline_records_archive). The record is marked as deleted and hidden from all views, but not permanently removed. Returns confirmation of the deletion. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | Yes | Pipeline record UUID · Format: UUID | ## Example prompts - "Delete the duplicate pipeline record I accidentally created for Smith Brokerage." - "Remove that test record from my pipeline, but double-check with me before deleting." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # pipeline_records_get > Get a single pipeline record by ID with full details including contact info, current stage, pipeline type, and stage-specific fields. Get a single pipeline record by ID with full details including contact info, current stage, pipeline type, and stage-specific fields. Use after [`pipeline_records_list`](/tools/pipelines/pipeline_records_list) when you need everything about one record. Returns the complete record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | Yes | Pipeline record UUID · Format: UUID | ## Example prompts - "Pull up the full pipeline record for Smith Brokerage with its stage details." - "What are the details on the Keystone Realty record, including stage-specific fields?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # pipeline_records_list > List pipeline records with filtering. List pipeline records with filtering. Use to browse a pipeline or find record IDs before get/update/move operations. Filter by stage, care status, priority, source, or search by name/email/title. Returns records with contact info and stage details. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `pipeline_type_id` | string | No | Filter by pipeline type · Format: UUID | | `stage_key` | string | No | Filter by stage key (e.g., "lead", "demo", "trial") | | `care_status` | enum | No | Filter by care status · One of: `no_status`, `cared`, `needs_care`, `didnt_care` | | `priority` | enum | No | Filter by priority level · One of: `low`, `medium`, `high`, `urgent` | | `source` | string | No | Filter by source | | `search` | string | No | Search by contact name, email, or record title | | `is_archived` | boolean | No | Include archived records (default: false) | | `page` | integer | No | Page number (default: 1) · Min: 1 | | `limit` | integer | No | Results per page (default: 25) · Max: 100 · Min: 1 | | `sort_by` | enum | No | Sort field · One of: `created_at`, `updated_at`, `estimated_ltv`, `expected_close_date`, `priority` | | `sort_order` | enum | No | Sort direction · One of: `asc`, `desc` | ## Example prompts - "List everyone sitting in the demo stage of my pipeline right now." - "Show urgent pipeline records that still need care, sorted by expected close date." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # pipeline_records_move_stage > Move a pipeline record to a new stage. Move a pipeline record to a new stage. Logs the stage transition in the activity history. Use [`pipeline_stages_list`](/tools/pipelines/pipeline_stages_list) to see available stage keys. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | Yes | Pipeline record UUID · Format: UUID | | `stage_key` | string | Yes | Target stage key (e.g., "demo", "trial", "paid") | | `notes` | string | No | Notes about why this record moved stages | ## Example prompts - "Move Smith Brokerage from demo to trial, they started their evaluation today." - "Advance the Keystone Realty record to the paid stage and note they signed yesterday." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # pipeline_records_restore > Restore an archived pipeline record back to active status. Restore an archived pipeline record back to active status. Use when a previously archived record becomes relevant again. Returns the restored record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | Yes | Pipeline record UUID · Format: UUID | ## Example prompts - "Restore the archived Hillcrest Lending record, they just reached back out." - "Bring the Smith Brokerage record back into my active pipeline view." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # pipeline_records_stats > Get pipeline statistics: funnel counts per stage, total LTV, total revenue, conversion rate, records needing follow-up, and records expiring soon. Get pipeline statistics: funnel counts per stage, total LTV, total revenue, conversion rate, records needing follow-up, and records expiring soon. Use to answer how a pipeline is doing or to decide where to focus follow-up. Returns the aggregate numbers only — use [`pipeline_records_list`](/tools/pipelines/pipeline_records_list) to see the underlying records. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `pipeline_type_id` | string | No | Filter stats by pipeline type · Format: UUID | ## Example prompts - "What is my pipeline conversion rate and total LTV right now?" - "How many pipeline records need follow-up or are expiring soon?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # pipeline_records_update > Update a pipeline record's fields — title, source, estimated_ltv, priority, notes, tags, record_data, and more. Update a pipeline record's fields — title, source, estimated_ltv, priority, notes, tags, record_data, and more. Only provided fields are updated. To change stage, use [`pipeline_records_move_stage`](/tools/pipelines/pipeline_records_move_stage) instead. Returns the updated record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | Yes | Pipeline record UUID · Format: UUID | | `title` | string | No | Record title | | `source` | string | No | Lead/record source | | `estimated_ltv` | number | No | Estimated lifetime value | | `current_revenue` | number | No | Current revenue amount | | `expected_close_date` | string | No | Expected conversion date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `expiration_date` | string | No | Expiration date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `priority` | enum | No | Priority level · One of: `low`, `medium`, `high`, `urgent` | | `notes` | string | No | Free-text notes | | `tags` | array of strings | No | Tags for categorization (replaces existing tags) | | `record_data` | object | No | Stage-specific fields (merged with existing) | | `probability` | integer | No | Close probability percentage (0-100) · Max: 100 · Min: 0 | | `care_status` | enum | No | Care status · One of: `no_status`, `cared`, `needs_care`, `didnt_care` | | `care_status_note` | string | No | Note for care status change | ## Example prompts - "Bump the Smith Brokerage record to urgent priority and set close probability to 80." - "Update the Keystone Realty record with a 24000 dollar estimated LTV and add my call notes." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # pipeline_stages_list > Get the ordered stages (funnel) for a specific pipeline type. Get the ordered stages (funnel) for a specific pipeline type. Each stage has a key, label, color, probability, and whether it is a default/final/lost stage. Use [`pipeline_types_list`](/tools/pipelines/pipeline_types_list) first to get the pipeline_type_id. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `pipeline_type_id` | string | Yes | Pipeline type UUID from [`pipeline_types_list`](/tools/pipelines/pipeline_types_list) · Format: UUID | ## Example prompts - "Show me the stages in my lender pipeline from first contact to close." - "What funnel steps does my vendor growth pipeline go through, in order?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # pipeline_types_list > List available pipeline types for the current user based on their role. List available pipeline types for the current user based on their role. System admins see the SaaS Growth Pipeline. Vendors and lenders see their industry-specific pipeline. Returns pipeline type IDs needed for other pipeline operations. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "Which pipelines do I have access to with my lender account?" - "List my available pipeline types so I can pick the right one." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # P&L statements > Analyze an uploaded profit-and-loss statement and predict expense categories. Analyze an uploaded profit-and-loss statement and predict expense categories. ## Tools (2) | Tool | Type | What it does | | --- | --- | --- | | [`analyze_pl_statement`](/tools/pl-statements/analyze_pl_statement) | Read-only | Analyze an uploaded Profit & Loss statement the caller owns. | | [`categorize_expense`](/tools/pl-statements/categorize_expense) | Read-only | Predict the expense category for a single ad-hoc expense input (description + optional vendor + optional amount). | --- # analyze_pl_statement > Analyze an uploaded Profit & Loss statement the caller owns. Analyze an uploaded Profit & Loss statement the caller owns. Returns the parsed summary (period, totals, line-item count, top categories), prior-period totals when available, and the AI-generated recommendations attached to the statement. The caller MUST own the statement — requests for statements belonging to another account return an error. Use when the user asks "what does my P&L tell me", "analyze my Q1 numbers", or similar. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `pl_statement_id` | string | Yes | UUID of the P&L statement to analyze. Must be owned by the caller. | ## Example prompts - "Analyze my Q1 profit and loss statement and tell me what stands out." - "What does my latest P&L say about my top expense categories?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # categorize_expense > Predict the expense category for a single ad-hoc expense input (description + optional vendor + optional amount). Predict the expense category for a single ad-hoc expense input (description + optional vendor + optional amount). Returns category, subcategory, confidence (0–1), and the source of the prediction (per-user vendor map, platform-wide vendor map, keyword rules, or none). NOT a write — does not record the expense. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `description` | string | No | Free-text description of the expense (required if vendor not given). | | `vendor` | string | No | Vendor or payee name. Strongest signal for the categorizer. | | `amount_cents` | integer | No | Amount in cents. Optional — used as a tie-breaker but not required. · Min: 0 | ## Example prompts - "How should I categorize a 450 dollar charge from Bay Photo Marketing?" - "What expense category does an 89 dollar lockbox purchase from SentriLock fall under?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # PM consultations > Manage property-management consultation requests from prospective landlord clients. Manage property-management consultation requests from prospective landlord clients. ## Tools (4) | Tool | Type | What it does | | --- | --- | --- | | [`pm_consultations_list`](/tools/pm-consultations/pm_consultations_list) | Read-only | Search property-management (PM) consultations — the funnel for turning landlord contacts into management clients. | | [`pm_consultations_get`](/tools/pm-consultations/pm_consultations_get) | Read-only | Get full details of one consultation by UUID. | | [`pm_consultations_create`](/tools/pm-consultations/pm_consultations_create) | Creates data | Start a PM consultation — a new conversation with a landlord about potentially handing over property management. | | [`pm_consultations_convert_to_tenancy`](/tools/pm-consultations/pm_consultations_convert_to_tenancy) | Creates data | Atomically mark a consultation as signed and create a linked tenancy. | --- # pm_consultations_convert_to_tenancy > Atomically mark a consultation as signed and create a linked tenancy. Atomically mark a consultation as signed and create a linked tenancy. Requires lease_id (the lease that now gets managed) and typically owner_client_id (the landlord as a client). The new tenancy automatically inherits the consultation's brokerage/team assignment. This is the canonical "we've signed this landlord, start managing the lease" action. Cannot convert a declined consultation. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `consultation_id` | string | Yes | UUID of the consultation to convert · Format: UUID | | `lease_id` | string | Yes | UUID of the lease that will now be PM-managed (required) · Format: UUID | | `owner_client_id` | string | No | UUID of the landlord as a client (typically client_type=landlord) · Format: UUID | | `management_fee_pct` | number | No | Actual fee on signing (default: proposed_management_fee_pct from consultation, or 10.00) · Max: 100 · Min: 0 | | `rent_collection_day` | number | No | Day of month for rent collection (default: 1) · Max: 31 · Min: 1 | | `notes` | string | No | Initial notes on the new tenancy · Max length: 10000 | ## Example prompts - "Marcus Bell signed the management agreement, convert his consultation and start managing the lease." - "Mark the Nair consultation as signed and set rent collection for the first." ## 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. --- # pm_consultations_create > Start a PM consultation — a new conversation with a landlord about potentially handing over property management. Start a PM consultation — a new conversation with a landlord about potentially handing over property management. Defaults stage='initial_inquiry'. Add property_listing_ids if the landlord has specific properties under discussion. Set estimated_monthly_revenue + close_probability to surface weighted pipeline value in stats. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `landlord_contact_id` | string | Yes | UUID of the landlord contact (required) · Format: UUID | | `property_listing_ids` | array of strings | No | UUIDs of listings the landlord is considering for PM · Format: UUID | | `stage` | enum | No | Initial stage (default: initial_inquiry) · One of: `initial_inquiry`, `property_walkthrough`, `proposal_sent`, `contract_negotiation`, `signed`, `declined`, `stalled` | | `proposed_management_fee_pct` | number | No | Proposed monthly management fee percentage (0-100) · Max: 100 · Min: 0 | | `proposed_leasing_fee_months` | number | No | Months of rent charged as leasing fee when placing a new tenant · Min: 0 | | `estimated_monthly_revenue` | number | No | Estimated recurring monthly revenue if signed · Min: 0 | | `close_probability` | number | No | Probability of closing (0-100, used for weighted pipeline stats) · Max: 100 · Min: 0 | | `stage_notes` | string | No | Notes about the current stage (discussion points, next steps, objections) · Max length: 10000 | ## Example prompts - "Start a management consultation with landlord Priya Nair for her duplex on Birchwood Ln." - "Open a PM consultation with the Garcias, 8 percent fee, around 600 monthly revenue." ## 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. --- # pm_consultations_get > Get full details of one consultation by UUID. Get full details of one consultation by UUID. Includes sensitive proposal terms (proposed_management_fee_pct, proposed_leasing_fee_months, estimated_monthly_revenue, close_probability) — caller must sanitize before any public AI summary. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `consultation_id` | string | Yes | UUID of the consultation · Format: UUID | ## Example prompts - "Pull up my consultation with landlord Marcus Bell, including the proposed management fee." - "What terms did I propose in the Ramos consultation, and the close probability?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # pm_consultations_list > Search property-management (PM) consultations — the funnel for turning landlord contacts into management clients. Search property-management (PM) consultations — the funnel for turning landlord contacts into management clients. Returns id, landlord_contact_id, stage, proposed_management_fee_pct, estimated_monthly_revenue, close_probability, next_meeting_at. Filter by stage to find consultations at a specific funnel step (e.g. stage='proposal_sent' for "who am I waiting on?"). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Free-text search (reserved) | | `stage` | enum | No | Filter by funnel stage · One of: `initial_inquiry`, `property_walkthrough`, `proposal_sent`, `contract_negotiation`, `signed`, `declined`, `stalled` | | `landlord_contact_id` | string | No | Filter to consultations with a specific landlord · Format: UUID | | `limit` | number | No | Maximum results (default: 25, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "Which landlords have I sent management proposals to and not heard back from?" - "List my property management consultations currently in contract negotiation." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Prospects (vendor pipeline) > Top-of-funnel vendor prospecting — create, update, stats, and lifecycle operations. Top-of-funnel vendor prospecting — create, update, stats, and lifecycle operations. ## Tools (8) | Tool | Type | What it does | | --- | --- | --- | | [`prospects_list`](/tools/prospects/prospects_list) | Read-only | Search for vendor prospects by name, status, vendor type, or interest level. | | [`prospects_get`](/tools/prospects/prospects_get) | Read-only | Get full details of a vendor prospect by UUID, including contact info, vendor type, interest level, priority, estimated lifetime value, notes, tags, and status history. | | [`prospects_create`](/tools/prospects/prospects_create) | Creates data | Create a new vendor prospect to track a potential partner. | | [`prospects_update`](/tools/prospects/prospects_update) | Updates data | Update an existing vendor prospect's information or status. | | [`prospects_stats`](/tools/prospects/prospects_stats) | Read-only | Get aggregate statistics for vendor prospects: total count, counts by status, counts by vendor type, counts by interest level, average estimated LTV. | | [`prospects_archive`](/tools/prospects/prospects_archive) | Updates data | Archive a vendor prospect to hide it from active views without deleting it. | | [`prospects_restore`](/tools/prospects/prospects_restore) | Updates data | Restore a previously archived vendor prospect back to active views. | | [`prospects_delete`](/tools/prospects/prospects_delete) | Irreversible | Permanently delete a vendor prospect. | --- # prospects_archive > Archive a vendor prospect to hide it from active views without deleting it. Archive a vendor prospect to hide it from active views without deleting it. Archived prospects can be restored later with [`prospects_restore`](/tools/prospects/prospects_restore). Use this for disqualified or lost prospects you want to declutter from your dashboard. Returns the archived record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `prospect_id` | string | Yes | UUID of the prospect to archive. Use [`prospects_list`](/tools/prospects/prospects_list) to find. · Format: UUID | ## Example prompts - "Archive the disqualified appraiser prospect so it stops cluttering my dashboard." - "Hide the Coastal Title prospect from my active list, the deal went cold." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # prospects_create > Create a new vendor prospect to track a potential partner. Create a new vendor prospect to track a potential partner. WORKFLOW: 1) Optionally use [`contacts_list`](/tools/contacts/contacts_list) to find the contact 2) Create the prospect with vendor_type and details. Returns the created prospect with ID and display_id. Interest level defaults to 'warm' and priority to 'medium' if not specified. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `contact_id` | string | No | UUID of an existing contact for this prospect. Use [`contacts_list`](/tools/contacts/contacts_list) to find. · Format: UUID | | `vendor_type` | string | Yes | Type of vendor (e.g. lender, inspector, escrow_officer, title_rep, appraiser, contractor, photographer) | | `title` | string | No | Title or name for this prospect record | | `source` | string | No | How you discovered this prospect (e.g. "referral", "networking event", "online search") | | `interest_level` | enum | No | Interest level of the prospect (default: warm) · One of: `cold`, `warm`, `hot` | | `priority` | enum | No | Priority for outreach (default: medium) · One of: `low`, `medium`, `high`, `urgent` | | `estimated_ltv` | number | No | Estimated lifetime value of this vendor relationship in dollars · Min: 0 | | `notes` | string | No | Additional notes about the prospect | | `tags` | array of strings | No | Tags for categorization (e.g. ["local", "high-volume", "spanish-speaking"]) | ## Example prompts - "Add Tom Avery from Summit Lending as a hot prospect worth about 15000." - "Create a new photographer prospect for Lena Brooks, met her at a networking event." ## 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. --- # prospects_delete > Permanently delete a vendor prospect. Permanently delete a vendor prospect. This is IRREVERSIBLE - the prospect will be hidden from all views including archived. The prospect must be archived first. For normal cleanup, use [`prospects_archive`](/tools/prospects/prospects_archive) instead, which is reversible. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `prospect_id` | string | Yes | UUID of the prospect to delete. Must be archived first. Use [`prospects_get`](/tools/prospects/prospects_get) to verify. · Format: UUID | ## Example prompts - "Permanently delete the duplicate prospect record I created for Summit Lending." - "Clear out that archived test prospect, but double-check with me before deleting." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # prospects_get > Get full details of a vendor prospect by UUID, including contact info, vendor type, interest level, priority, estimated lifetime value, notes, tags, and status history. Get full details of a vendor prospect by UUID, including contact info, vendor type, interest level, priority, estimated lifetime value, notes, tags, and status history. Returns all fields. If you don't have the UUID, use [`prospects_list`](/tools/prospects/prospects_list) first. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `prospect_id` | string | Yes | UUID of the prospect. Use [`prospects_list`](/tools/prospects/prospects_list) to find IDs. · Format: UUID | ## Example prompts - "Pull up everything on the prospect Rosa Delgado, including notes and status history." - "What is the estimated lifetime value on my Coastal Title prospect?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # prospects_list > Search for vendor prospects by name, status, vendor type, or interest level. Search for vendor prospects by name, status, vendor type, or interest level. Returns pagination info (total_count, has_more, offset, limit). Results include: id, display_id, title, vendor_type, status, interest_level, priority, estimated_ltv, care_status, contact info, created_at. Filter by status (identified/researching/outreach/responded/nurturing/converted/disqualified/lost), interest_level (cold/warm/hot), priority (low/medium/high/urgent), or vendor_type. For a specific prospect by ID, use [`prospects_get`](/tools/prospects/prospects_get) instead. For aggregate stats, use [`prospects_stats`](/tools/prospects/prospects_stats). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term - matches against title, notes (case-insensitive partial match) | | `status` | enum | No | Filter by status. identified=new prospect, researching=gathering info, outreach=initial contact, responded=they replied, nurturing=building relationship, converted=became partner, disqualified=not a fit, lost=went cold (default: all) · One of: `all`, `identified`, `researching`, `outreach`, `responded`, `nurturing`, `converted`, `disqualified`, `lost` | | `vendor_type` | string | No | Filter by vendor type (e.g. lender, inspector, escrow_officer, title_rep, appraiser, contractor, photographer) | | `interest_level` | enum | No | Filter by interest level (default: all) · One of: `all`, `cold`, `warm`, `hot` | | `priority` | enum | No | Filter by priority (default: all) · One of: `all`, `low`, `medium`, `high`, `urgent` | | `care_status` | enum | No | Filter by care status (default: all) · One of: `all`, `no_status`, `cared`, `needs_care`, `didnt_care` | | `date_from` | string | No | Show prospects created on or after this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `date_to` | string | No | Show prospects created on or before this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `archived` | boolean | No | Include archived prospects (default: false) | | `limit` | number | No | Maximum results (default: 50, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "Show me all my hot lender prospects still in the outreach stage." - "List inspector prospects added since March that have responded to me." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # prospects_restore > Restore a previously archived vendor prospect back to active views. Restore a previously archived vendor prospect back to active views. Reverses the effect of [`prospects_archive`](/tools/prospects/prospects_archive). Returns the restored record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `prospect_id` | string | Yes | UUID of the prospect to restore. Must be currently archived. · Format: UUID | ## Example prompts - "Restore the archived Tom Avery prospect, he just emailed me back." - "Bring my Coastal Title prospect back into the active pipeline." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # prospects_stats > Get aggregate statistics for vendor prospects: total count, counts by status, counts by vendor type, counts by interest level, average estimated LTV. Get aggregate statistics for vendor prospects: total count, counts by status, counts by vendor type, counts by interest level, average estimated LTV. Use this for dashboard metrics. Does NOT return individual records - use [`prospects_list`](/tools/prospects/prospects_list) for that. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `period` | enum | No | Time period for stats (default: 1_month) · One of: `1_day`, `1_week`, `1_month`, `3_months`, `1_year`, `ytd`, `all` | ## Example prompts - "How many vendor prospects did I add this month, broken down by status?" - "What is my average prospect lifetime value over the past year?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # prospects_update > Update an existing vendor prospect's information or status. ```text 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`](/tools/prospects/prospects_list) to find. · Format: UUID | | `contact_id` | string | No | Updated contact ID. Use [`contacts_list`](/tools/contacts/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. --- # Referrals > Agent-to-agent referrals — create, update, stats, and lifecycle operations. Agent-to-agent referrals — create, update, stats, and lifecycle operations. ## Tools (8) | Tool | Type | What it does | | --- | --- | --- | | [`referrals_list`](/tools/referrals/referrals_list) | Read-only | Search for referrals by name, status, type, or date range. | | [`referrals_get`](/tools/referrals/referrals_get) | Read-only | Get full details of a referral by UUID, including referred person info, referring agent, receiving agent, financial details, and linked escrow. | | [`referrals_create`](/tools/referrals/referrals_create) | Creates data | Create a new referral to track an agent-to-agent referral. | | [`referrals_update`](/tools/referrals/referrals_update) | Updates data | Update an existing referral's information or status. | | [`referrals_stats`](/tools/referrals/referrals_stats) | Read-only | Get aggregate statistics for referrals: total count, counts by status, total fees earned, total fees pending. | | [`referrals_archive`](/tools/referrals/referrals_archive) | Updates data | Archive a referral to hide it from active views without deleting it. | | [`referrals_restore`](/tools/referrals/referrals_restore) | Updates data | Restore a previously archived referral back to active views. | | [`referrals_delete`](/tools/referrals/referrals_delete) | Irreversible | Permanently delete a referral. | --- # referrals_archive > Archive a referral to hide it from active views without deleting it. Archive a referral to hide it from active views without deleting it. Archived referrals can be restored later with [`referrals_restore`](/tools/referrals/referrals_restore). Use this for old or inactive referrals you want to declutter from your dashboard. Returns the archived record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `referral_id` | string | Yes | UUID of the referral to archive. Use [`referrals_list`](/tools/referrals/referrals_list) to find. · Format: UUID | ## Example prompts - "Archive the expired referral for Mark Tibbets to clean up my dashboard." - "Hide that old declined referral from my active list without deleting it." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # referrals_create > Create a new referral to track an agent-to-agent referral. Create a new referral to track an agent-to-agent referral. WORKFLOW: 1) Optionally use [`leads_list`](/tools/leads/leads_list) or [`contacts_list`](/tools/contacts/contacts_list) to find the referred person 2) Create the referral with referred person info and receiving agent details. Returns the created referral with ID and display_id. If referral_fee_percentage is not specified, it defaults to your brokerage's configured rate, or 25%. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `referred_name` | string | No | Name of the referred person | | `referred_email` | string | No | Email of the referred person | | `referred_phone` | string | No | Phone number of the referred person | | `referred_lead_id` | string | No | UUID of an existing lead being referred. Use [`leads_list`](/tools/leads/leads_list) to find. · Format: UUID | | `referred_contact_id` | string | No | UUID of an existing contact being referred. Use [`contacts_list`](/tools/contacts/contacts_list) to find. · Format: UUID | | `receiving_agent_name` | string | No | Name of the agent receiving the referral | | `receiving_agent_email` | string | No | Email of the receiving agent | | `receiving_agent_id` | string | No | UUID of the receiving agent if they are on the platform · Format: UUID | | `referring_agent_name` | string | No | Name of the referring agent (auto-filled from current user if omitted) | | `referring_agent_email` | string | No | Email of the referring agent | | `referral_type` | enum | No | Type of referral (default: buyer) · One of: `buyer`, `seller`, `both` | | `referral_fee_percentage` | number | No | Referral fee percentage (default: your brokerage's configured rate, or 25%) · Max: 100 · Min: 0 | | `referral_source` | string | No | How the referral originated (e.g. "sphere of influence", "past client", "open house") | | `notes` | string | No | Additional notes about the referral | ## Example prompts - "Refer the Garcias to Dana Cole in Phoenix with a 25 percent fee." - "Create a buyer referral sending Mark Tibbets to agent Joy Lin at Coastal Realty." ## 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. --- # referrals_delete > Permanently delete a referral. Permanently delete a referral. This is IRREVERSIBLE - the referral will be hidden from all views including archived. The referral must be archived first. For normal cleanup, use [`referrals_archive`](/tools/referrals/referrals_archive) instead, which is reversible. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `referral_id` | string | Yes | UUID of the referral to delete. Must be archived first. Use [`referrals_get`](/tools/referrals/referrals_get) to verify. · Format: UUID | ## Example prompts - "Permanently delete the duplicate referral I logged twice for the Garcias." - "Remove that archived test referral for good, but double-check with me before deleting." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # referrals_get > Get full details of a referral by UUID, including referred person info, referring agent, receiving agent, financial details, and linked escrow. Get full details of a referral by UUID, including referred person info, referring agent, receiving agent, financial details, and linked escrow. Returns all fields including status history timestamps. If you don't have the UUID, use [`referrals_list`](/tools/referrals/referrals_list) first. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `referral_id` | string | Yes | UUID of the referral. Use [`referrals_list`](/tools/referrals/referrals_list) to find IDs. · Format: UUID | ## Example prompts - "Pull up the full referral details for the Garcias, including the fee terms." - "What is the status history on my referral to agent Dana Cole?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # referrals_list > Search for referrals by name, status, type, or date range. Search for referrals by name, status, type, or date range. Returns pagination info (total_count, has_more, offset, limit). Results include: id, display_id, referred_name, referred_email, referring_agent_name, receiving_agent_name, referral_type, status, referral_fee_percentage, created_at. Filter by status (submitted/accepted/active/closed/paid/declined/expired), type (buyer/seller/both), or date range. For a specific referral by ID, use [`referrals_get`](/tools/referrals/referrals_get) instead. For aggregate stats, use [`referrals_stats`](/tools/referrals/referrals_stats). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term - matches against referred_name, referred_email, referring_agent_name, receiving_agent_name (case-insensitive partial match) | | `status` | enum | No | Filter by status. submitted=new, accepted=agreed, active=in progress, closed=transaction closed, paid=fee collected, declined=rejected, expired=timed out (default: all) · One of: `all`, `submitted`, `accepted`, `active`, `closed`, `paid`, `declined`, `expired` | | `referral_type` | enum | No | Filter by referral type (default: all) · One of: `all`, `buyer`, `seller`, `both` | | `date_from` | string | No | Show referrals submitted on or after this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `date_to` | string | No | Show referrals submitted on or before this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `archived` | boolean | No | Include archived referrals (default: false) | | `limit` | number | No | Maximum results (default: 50, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "Show me all my active referrals and which agents are working them." - "List referrals I submitted this quarter that have not been paid yet." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # referrals_restore > Restore a previously archived referral back to active views. Restore a previously archived referral back to active views. Reverses the effect of [`referrals_archive`](/tools/referrals/referrals_archive). Returns the restored record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `referral_id` | string | Yes | UUID of the referral to restore. Must be currently archived. · Format: UUID | ## Example prompts - "Restore the archived Garcia referral, that deal is back on again." - "Unarchive my referral to Joy Lin so I can keep tracking it." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # referrals_stats > Get aggregate statistics for referrals: total count, counts by status, total fees earned, total fees pending. Get aggregate statistics for referrals: total count, counts by status, total fees earned, total fees pending. Use this for dashboard metrics. Does NOT return individual records - use [`referrals_list`](/tools/referrals/referrals_list) for that. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `period` | enum | No | Time period for stats (default: 1_month) · One of: `1_day`, `1_week`, `1_month`, `3_months`, `1_year`, `ytd`, `all` | ## Example prompts - "How much referral income have I earned year to date, and what is pending?" - "Give me a breakdown of my referrals by status for the last three months." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # referrals_update > Update an existing referral's information or status. ```text Update an existing referral's information or status. Only provided fields are updated - omitted fields remain unchanged. Common uses: status change (submitted->accepted->active->closed->paid), add financial details, link escrow. Returns the updated referral record. ``` ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `referral_id` | string | Yes | UUID of the referral to update (required). Use [`referrals_list`](/tools/referrals/referrals_list) to find. · Format: UUID | | `referred_name` | string | No | Updated referred person name | | `referred_email` | string | No | Updated referred person email | | `referred_phone` | string | No | Updated referred person phone | | `referred_lead_id` | string | No | Updated lead ID · Format: UUID | | `referred_contact_id` | string | No | Updated contact ID · Format: UUID | | `referring_agent_name` | string | No | Updated referring agent name | | `referring_agent_email` | string | No | Updated referring agent email | | `receiving_agent_id` | string | No | Updated receiving agent ID · Format: UUID | | `receiving_agent_name` | string | No | Updated receiving agent name | | `receiving_agent_email` | string | No | Updated receiving agent email | | `referral_type` | enum | No | Updated referral type · One of: `buyer`, `seller`, `both` | | `referral_source` | string | No | Updated referral source | | `notes` | string | No | Updated notes | | `status` | enum | No | Updated status · One of: `submitted`, `accepted`, `active`, `closed`, `paid`, `declined`, `expired` | | `referral_fee_percentage` | number | No | Updated fee percentage · Max: 100 · Min: 0 | | `transaction_amount` | number | No | Transaction amount when closed · Min: 0 | | `referral_fee_amount` | number | No | Actual referral fee amount · Min: 0 | | `escrow_id` | string | No | Link to an escrow when the referral leads to a transaction · Format: UUID | | `care_status` | enum | No | Care status for tracking · One of: `no_status`, `cared`, `needs_care`, `didnt_care` | ## Example prompts - "Mark the Garcia referral as closed with a 450000 transaction amount." - "Update my referral to Dana Cole to paid, the fee check came in." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # Rental applications > Receive and process rental applications for the property-management vertical. Receive and process rental applications for the property-management vertical. ## Tools (4) | Tool | Type | What it does | | --- | --- | --- | | [`rental_applications_list`](/tools/rental-applications/rental_applications_list) | Read-only | Search rental applications by decision, applicant, listing, or free-text query. | | [`rental_applications_get`](/tools/rental-applications/rental_applications_get) | Read-only | Get full details of one rental application by UUID. | | [`rental_applications_approve`](/tools/rental-applications/rental_applications_approve) | Updates data | Mark a rental application as approved. | | [`rental_applications_convert_to_lease`](/tools/rental-applications/rental_applications_convert_to_lease) | Creates data | Atomically approve (if pending) and create a lease from an approved application. | --- # rental_applications_approve > Mark a rental application as approved. Mark a rental application as approved. Stamps reviewed_at=NOW. Idempotent — calling on an already-approved application is a no-op. Cannot approve a withdrawn application (will error). Does NOT create a lease — call [`rental_applications_convert_to_lease`](/tools/rental-applications/rental_applications_convert_to_lease) for that atomic flow. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `application_id` | string | Yes | UUID of the application to approve · Format: UUID | | `reason` | string | No | Optional approval note for audit trail (e.g., "Strong credit and income verified") · Max length: 2000 | ## Example prompts - "Approve Tia Moreno's application, her credit and income both checked out." - "Mark the Birchwood Ln application approved with a note that employment was verified." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # rental_applications_convert_to_lease > Atomically approve (if pending) and create a lease from an approved application. Atomically approve (if pending) and create a lease from an approved application. Links the new lease to the application via rental_application_id. The new lease automatically inherits the application's listing and brokerage/team assignment. Cannot convert denied or withdrawn applications. Returns the new lease record. This is the canonical "I've decided to sign this tenant" action. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `application_id` | string | Yes | UUID of the application to convert · Format: UUID | | `lease_start` | string | Yes | Lease start date (ISO format, YYYY-MM-DD) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `lease_end` | string | Yes | Lease end date (ISO format, YYYY-MM-DD) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `monthly_rent` | number | Yes | Monthly rent amount · Min: 0 | | `security_deposit` | number | No | Security deposit amount · Min: 0 | | `lease_type` | enum | No | Lease type (default: residential) · One of: `residential`, `commercial`, `short_term` | | `landlord_contact_id` | string | No | UUID of the landlord contact · Format: UUID | | `renter_client_id` | string | No | UUID of the renter client. If not provided, the agent should create a client with client_type=tenant first via [`clients_create`](/tools/clients/clients_create) and link it here. · Format: UUID | | `commission_amount` | number | No | Agent commission for this lease · Min: 0 | | `notes` | string | No | Lease notes · Max length: 10000 | ## Example prompts - "Sign Tia Moreno as the tenant, twelve month lease at 2400 a month starting July 1." - "Convert the approved Birchwood Ln application into a lease with a 2400 deposit." ## 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. --- # rental_applications_get > Get full details of one rental application by UUID. Get full details of one rental application by UUID. Returns all application fields including credit_score, monthly_income, employment_status, background_check_status, eviction_history (sensitive — caller must sanitize before AI use). Returns decision, decision_reason, reviewed_at for audit trail. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `application_id` | string | Yes | UUID of the rental application · Format: UUID | ## Example prompts - "Show me the full application for 412 Birchwood Ln, including credit score and income." - "Pull up Tia Moreno's application details before I make a decision." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # rental_applications_list > Search rental applications by decision, applicant, listing, or free-text query. Search rental applications by decision, applicant, listing, or free-text query. Returns id, listing_id, applicant_contact_id, decision, submitted_at, reviewed_at. Use decision='pending' or 'reviewing' to find applications needing a decision. Sensitive financial fields (credit_score, monthly_income) are NOT returned in list mode — fetch with [`rental_applications_get`](/tools/rental-applications/rental_applications_get) when needed for decision context. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Free-text search (reserved — use decision/applicant/listing filters for now) | | `decision` | enum | No | Filter by decision status. pending=not yet reviewed, reviewing=in progress, approved/denied=decided, withdrawn=applicant pulled out · One of: `pending`, `reviewing`, `approved`, `denied`, `withdrawn` | | `applicant_contact_id` | string | No | Filter to applications by a specific applicant · Format: UUID | | `listing_id` | string | No | Filter to applications for a specific listing · Format: UUID | | `limit` | number | No | Maximum results (default: 25) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination · Min: 0 | ## Example prompts - "Which rental applications are still pending a decision on my Birchwood Ln listing?" - "List all applications from Tia Moreno across my rental listings." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Reporting & insights > Production reports, lead-source ROI, anniversaries, hot-lead lists, buyer matching, and close-probability estimates. Production reports, lead-source ROI, anniversaries, hot-lead lists, buyer matching, and close-probability estimates. ## Tools (7) | Tool | Type | What it does | | --- | --- | --- | | [`get_production_report`](/tools/reporting/get_production_report) | Read-only | Get a production report showing volume, units closed, and commission earned for a time period. | | [`get_lead_source_roi`](/tools/reporting/get_lead_source_roi) | Read-only | Get lead conversion data grouped by source. | | [`get_client_anniversaries`](/tools/reporting/get_client_anniversaries) | Read-only | Get clients with upcoming home purchase anniversaries for sphere marketing. | | [`get_hot_leads`](/tools/reporting/get_hot_leads) | Read-only | Get active leads sorted by status priority and recency for prospecting. | | [`suggest_next_action`](/tools/reporting/suggest_next_action) | Read-only | Get data-driven suggestions for next steps. | | [`match_buyers_to_listings`](/tools/reporting/match_buyers_to_listings) | Read-only | Find buyer clients whose saved price range overlaps with a listing's price (within 10%). | | [`predict_close_probability`](/tools/reporting/predict_close_probability) | Read-only | Estimate close likelihood for an escrow based on simple heuristics: contingency removal status and days to closing date. | --- # get_client_anniversaries > Get clients with upcoming home purchase anniversaries for sphere marketing. Get clients with upcoming home purchase anniversaries for sphere marketing. A proven touchpoint for staying in contact with past clients and generating referrals. Returns: client name, property address, purchase date, anniversary date, years since purchase. Send an anniversary card or call to maintain the relationship. Also useful for triggering annual home value updates or refinance discussions. Results sorted by anniversary date. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `days_ahead` | number | No | Look ahead this many days for upcoming anniversaries. Default: 30 days gives time to prepare cards. · Max: 90 · Min: 1 | | `include_past` | number | No | Include anniversaries from past N days for recently missed ones. Default: 7 days. · Max: 30 · Min: 0 | ## Example prompts - "Which past clients have home purchase anniversaries coming up in the next 30 days?" - "Pull anniversaries for the next two weeks so I can mail cards, plus any missed last week." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # get_hot_leads > Get active leads sorted by status priority and recency for prospecting. Get active leads sorted by status priority and recency for prospecting. Returns leads in priority order: qualified first, then contacted, then new — with most recent first within each group. Use this to build a daily call list. Note: this is a simple sort by status and date, not a predictive scoring model. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `min_score` | number | No | Minimum score 0-100 to include. Default: 50. Use 70+ for hot leads only, 0 for all leads ranked. · Max: 100 · Min: 0 | | `lead_type` | enum | No | Filter by lead type. buyer=buying clients, seller=listing prospects, both=investor/dual leads, all=no filter. Default: all. · One of: `buyer`, `seller`, `both`, `all` | | `limit` | number | No | Maximum results. Default: 10. Your daily call list should be 10-20 leads. · Max: 100 · Min: 1 | ## Example prompts - "Build me a call list of my ten hottest buyer leads for this morning." - "Show qualified seller leads scoring 70 or above so I can prioritize listing appointments." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # get_lead_source_roi > Get lead conversion data grouped by source. Get lead conversion data grouped by source. Returns for each source: total leads, converted count, and conversion rate. Sources include: referral, zillow, realtor.com, open_house, sign_call, website, social_media, etc. Note: cost per lead and ROI are not tracked — only conversion rates from existing data. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `period` | enum | No | Time period to analyze. Longer periods give more reliable conversion data. Default: ytd. · One of: `ytd`, `last_6_months`, `last_year`, `all_time` | | `min_leads` | number | No | Minimum leads to include a source in results. Use 5-10 for meaningful averages. Default: 1. · Max: 100 · Min: 1 | ## Example prompts - "Which lead sources convert best for me over the last six months?" - "Compare conversion rates by source year to date, only counting sources with five-plus leads." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # get_production_report > Get a production report showing volume, units closed, and commission earned for a time period. Get a production report showing volume, units closed, and commission earned for a time period. Essential for tracking business performance and setting goals. Returns: total closed volume, units closed, gross commission, average deal size, and comparison to prior period. Use period parameter for standard ranges (ytd, mtd, qtd) or custom for specific date ranges. group_by allows breakdown by month/quarter to see trends. include_pending adds pipeline value for forecasting. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `period` | enum | No | Time period for the report. ytd=year to date (most common), mtd=month to date, qtd=quarter to date, custom=use start_date/end_date. Default: ytd. · One of: `ytd`, `mtd`, `qtd`, `last_month`, `last_quarter`, `last_year`, `all_time`, `custom` | | `start_date` | string | No | Start date for custom period. Required when period="custom". (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `end_date` | string | No | End date for custom period. Required when period="custom". (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `include_pending` | boolean | No | Include pending escrows in pipeline forecast. Default: true. Set false for closed-only report. | | `group_by` | enum | No | Group results by time period for trend analysis. none=single total, month=monthly breakdown. Default: none. · One of: `month`, `quarter`, `year`, `none` | ## Example prompts - "How much volume and commission have I closed year to date compared to last year?" - "Break down my closed units and GCI by quarter for 2025, excluding pending escrows." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # match_buyers_to_listings > Find buyer clients whose saved price range overlaps with a listing's price (within 10%). Find buyer clients whose saved price range overlaps with a listing's price (within 10%). Returns the listing details and a list of potential buyer clients filtered by price criteria. Results are filtered by data, not recommended — the agent should independently evaluate suitability for each buyer. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `client_id` | string | No | UUID of the buyer client to match. Their saved preferences (budget, beds, baths, areas) are used for matching. · Format: UUID | | `min_price` | number | No | Override client minimum price. Useful for expanding search if few matches. · Min: 0 | | `max_price` | number | No | Override client maximum price. Useful for stretching budget for right property. · Min: 0 | | `min_beds` | number | No | Minimum bedrooms filter. · Max: 10 · Min: 0 | | `min_baths` | number | No | Minimum bathrooms filter. · Max: 10 · Min: 0 | | `property_types` | array of enum | No | Property types to search. Default: all types client is interested in. · Values: `single_family`, `condo`, `townhouse`, `multi_family`, `land`, `commercial` | | `cities` | array of strings | No | Cities to search in. Default: cities from client preferences. | | `limit` | number | No | Maximum results. Default: 10. Use 20-30 for comprehensive showing tour. · Max: 50 · Min: 1 | ## Example prompts - "Which active listings fit the Garcias budget and their three-bedroom requirement in Bakersfield?" - "Stretch Tom and Priya's max price to 525k and rerun their listing matches." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # predict_close_probability > Estimate close likelihood for an escrow based on simple heuristics: contingency removal status and days to closing date. Estimate close likelihood for an escrow based on simple heuristics: contingency removal status and days to closing date. Returns a rough percentage (not a statistical model) and the factors used. This is an internal planning heuristic only — do not share the percentage with clients or present it as a factual prediction. The agent should apply their own experience and judgment. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | Yes | UUID of the escrow to analyze. Use [`escrows_list`](/tools/escrows/escrows_list) to find ID. · Format: UUID | ## Example prompts - "How likely is the Birchwood Ln escrow to close on time, roughly?" - "Give me a rough close-probability read on the Hammond escrow for my own planning." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # suggest_next_action > Get data-driven suggestions for next steps. Get data-driven suggestions for next steps. Two modes: (1) HOLISTIC — call with NO args to get the top highest-impact next moves across hot leads, closing escrows, and stale clients (use this for prompts like "what's my next move?" or "what should I do next?"). (2) PER-ENTITY — pass entity_type ('lead' | 'client' | 'escrow') AND entity_id to get suggestions scoped to one specific record. Returns suggestions with priority levels and reasons. These are suggestions for internal planning — the licensed agent must exercise independent professional judgment on all actions. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `entity_type` | enum | No | OPTIONAL. Type of entity to analyze. Omit for holistic mode. · One of: `lead`, `client`, `escrow` | | `entity_id` | string | No | OPTIONAL. UUID of the entity to analyze. Omit for holistic mode. If provided, entity_type is also required. · Format: UUID | ## Example prompts - "What's my highest-impact next move right now across leads and escrows?" - "What should I do next on the escrow for 412 Birchwood Ln?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Review requests > Find clients from recently closed escrows, draft a review request email, and send it after your explicit confirmation. Find clients from recently closed escrows, draft a review request email, and send it after your explicit confirmation. ## Tools (3) | Tool | Type | What it does | | --- | --- | --- | | [`list_clients_pending_review_request`](/tools/review-requests/list_clients_pending_review_request) | Read-only | List the agent's closed escrows that are eligible for a Google review request but haven't been asked yet. | | [`draft_review_request_email`](/tools/review-requests/draft_review_request_email) | Read-only | Generate the personalized subject, plain-text body, HTML body, and Google write-review URL for a review request email tied to a specific closed escrow. | | [`send_review_request`](/tools/review-requests/send_review_request) | Creates data + external action | Send a review request email NOW for a specific closed escrow. | --- # draft_review_request_email > Generate the personalized subject, plain-text body, HTML body, and Google write-review URL for a review request email tied to a specific closed escrow. Generate the personalized subject, plain-text body, HTML body, and Google write-review URL for a review request email tied to a specific closed escrow. Read-only — does NOT send. Use this BEFORE [`send_review_request`](/tools/review-requests/send_review_request) so the user can preview and edit the draft in chat. The tool also reports `suppressed: true` (with a reason) if the recipient is on the email suppression list — the assistant should surface that to the user instead of proceeding to send. Any reviewer comment fields present in related data are sanitized to strip protected-characteristic and personal information before any AI processing. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | Yes | Identifier of the closed escrow. NOTE: escrow IDs are text identifiers (e.g. "ESC-2026-0042"), not UUIDs. Use [`list_clients_pending_review_request`](/tools/review-requests/list_clients_pending_review_request) or [`escrows_list`](/tools/escrows/escrows_list) to discover it. · Max length: 100 · Min length: 1 | | `tone` | enum | No | Tone variant for the email copy. "warm" is the default in the personalization service; choose explicitly if the user asks for a different feel. · One of: `warm`, `professional`, `casual` | ## Example prompts - "Draft a warm review request email for the Garcias closing so I can preview it." - "Write a professional-tone review ask for escrow ESC-2026-0042 before we send anything." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # list_clients_pending_review_request > List the agent's closed escrows that are eligible for a Google review request but haven't been asked yet. List the agent's closed escrows that are eligible for a Google review request but haven't been asked yet. A closing is eligible when it has a recorded close date within the days_since_close window AND no review request has been sent to the same client for that escrow in the last 60 days. Use when the user asks "who should I ask for a review?", "any closings I forgot to follow up on?", or similar. Returns one entry per pending closing with the data needed to draft a request: escrow_id, client_name, property_address, close_date, days_since_close. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `days_since_close` | integer | No | Window of closings to consider, measured from the actual close-of-escrow date (or the scheduled closing date when no actual date is recorded) up to today. Default 7 — matches the typical post-close cooling-off period used by the auto-send scheduler. · Max: 365 · Min: 1 | ## Example prompts - "Who should I ask for a Google review from my recent closings?" - "Any closings in the last 30 days where I forgot to request a review?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # send_review_request > Send a review request email NOW for a specific closed escrow. Send a review request email NOW for a specific closed escrow. **REQUIRES EXPLICIT USER CONFIRMATION IN CHAT BEFORE EXECUTION.** The assistant MUST first call [`draft_review_request_email`](/tools/review-requests/draft_review_request_email) to show the user the proposed subject + body, and MUST receive an unambiguous "yes, send it" (or equivalent confirmation) from the user before invoking this tool. This is a write tool that sends a real email. The service enforces the email suppression list, blocks repeat sends to the same client for the same escrow within 60 days, and applies the per-user limit of 50 sends per day — the same safeguards enforced by the REST endpoint. Returns `{ message_id, sent_at, status }` on success or a structured `skipped_*` / `error` outcome that explains why the send did not happen. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `escrow_id` | string | Yes | Identifier of the closed escrow. A text identifier (e.g. "ESC-2026-0042"), not a UUID. · Max length: 100 · Min length: 1 | | `template_variant` | enum | No | Tone variant to send. Defaults to the user's saved review-request tone preference (typically "warm"). Pick explicitly when the user asked for a specific tone in their confirmation. · One of: `warm`, `professional`, `casual` | | `custom_body` | string | No | Optional custom body override. The current template does NOT include this text in the sent email — it is recorded on the audit trail only. Pass it when the user dictates exact words, but be aware the recipient still receives the standard template body for now. · Max length: 5000 | ## Example prompts - "Yes, send that review request to the Garcias now, the warm version." - "Go ahead and send the review email for ESC-2026-0107 with the casual tone." ## Safety **Creates data + external action.** Creates a record and triggers an action in a connected external service. --- # Showings > Schedule, track, and log property showings, including buyer feedback. Schedule, track, and log property showings, including buyer feedback. ## Tools (8) | Tool | Type | What it does | | --- | --- | --- | | [`showings_list`](/tools/showings/showings_list) | Read-only | Search for property showings by address, status, type, or date range. | | [`showings_get`](/tools/showings/showings_get) | Read-only | Get full details of a showing by UUID, including listing and contact information. | | [`showings_create`](/tools/showings/showings_create) | Creates data | Schedule a new property showing. | | [`showings_update`](/tools/showings/showings_update) | Updates data | Update an existing showing's information or status. | | [`showings_stats`](/tools/showings/showings_stats) | Read-only | Get aggregate statistics for showings: total count, upcoming count, counts by status, counts by type. | | [`showings_archive`](/tools/showings/showings_archive) | Updates data | Archive a showing to hide it from active views without deleting it. | | [`showings_restore`](/tools/showings/showings_restore) | Updates data | Restore a previously archived showing back to active views. | | [`showings_delete`](/tools/showings/showings_delete) | Irreversible | Permanently delete a showing. | --- # showings_archive > Archive a showing to hide it from active views without deleting it. Archive a showing to hide it from active views without deleting it. Archived showings can be restored later with [`showings_restore`](/tools/showings/showings_restore). Use this for past showings you want to declutter from your dashboard. Returns the archived record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `showing_id` | string | Yes | UUID of the showing to archive. Use [`showings_list`](/tools/showings/showings_list) to find. · Format: UUID | ## Example prompts - "Archive that cancelled showing at 76 Pinehurst Ct to clean up my dashboard." - "Tidy up by archiving last month's completed showing at 412 Birchwood Ln." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # showings_create > Schedule a new property showing. Schedule a new property showing. WORKFLOW: 1) Optionally use [`listings_list`](/tools/listings/listings_list) to find the listing 2) Optionally use [`contacts_list`](/tools/contacts/contacts_list) to find the contact 3) Create the showing with address, date, and time. Returns the created showing with ID. Required fields: address, showing_date, showing_time. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `address` | string | Yes | Property address for the showing (required) | | `showing_date` | string | Yes | Date of the showing (required) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `showing_time` | string | Yes | Time of the showing in HH:MM format (required), e.g. "14:00" | | `listing_id` | string | No | UUID of the associated listing (optional). Use [`listings_list`](/tools/listings/listings_list) to find. · Format: UUID | | `contact_id` | string | No | UUID of the associated contact (optional). Use [`contacts_list`](/tools/contacts/contacts_list) to find. · Format: UUID | | `appointment_id` | string | No | UUID of the associated appointment (optional). Use [`appointments_list`](/tools/appointments/appointments_list) to find. · Format: UUID | | `showing_type` | enum | No | Type of showing (default: first_showing) · One of: `first_showing`, `follow_up`, `final_walkthrough`, `inspection`, `appraisal` | | `access_type` | string | No | Access type, e.g. "lockbox", "agent_present", "owner_present" | | `lockbox_code` | string | No | Lockbox code for property access | | `access_notes` | string | No | Notes about property access instructions | | `showing_status` | enum | No | Initial status (default: pending) · One of: `pending`, `confirmed`, `completed`, `cancelled`, `no_show` | ## Example prompts - "Schedule a first showing at 412 Birchwood Ln this Saturday at 2pm for the Garcias." - "Book a final walkthrough at 1530 Kern River Rd on June 27 at 10am, lockbox access." ## 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. --- # showings_delete > Permanently delete a showing. Permanently delete a showing. This is IRREVERSIBLE - the showing will be hidden from all views, including archived. The showing must be archived first. For normal cleanup, use [`showings_archive`](/tools/showings/showings_archive) instead which is reversible. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `showing_id` | string | Yes | UUID of the showing to delete. Must be archived first. Use [`showings_get`](/tools/showings/showings_get) to verify. · Format: UUID | ## Example prompts - "Permanently delete that duplicate showing entry for 88 Calloway Dr." - "Remove the old test showing at 12 Maple Ct for good, but double-check with me before deleting." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it. --- # showings_get > Get full details of a showing by UUID, including listing and contact information. Get full details of a showing by UUID, including listing and contact information. Returns address, date/time, status, type, access info, feedback, notes, and joined listing + contact details. If you don't have the UUID, use [`showings_list`](/tools/showings/showings_list) first. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `showing_id` | string | Yes | UUID of the showing. Use [`showings_list`](/tools/showings/showings_list) to find IDs. · Format: UUID | ## Example prompts - "Pull full details on tomorrow's showing at 88 Calloway Dr, including access notes." - "What's the lockbox info and client feedback for the Birchwood Ln showing?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # showings_list > Search for property showings by address, status, type, or date range. Search for property showings by address, status, type, or date range. Returns pagination info (total_count, has_more, offset, limit). Results include: id, address, showing_date, showing_time, showing_status, showing_type, access_type, listing address/photo, contact name, agent_notes, created_at. Filter by status (pending/confirmed/completed/cancelled/no_show), type (first_showing/follow_up/final_walkthrough/inspection/appraisal), or date range. For a specific showing by ID, use [`showings_get`](/tools/showings/showings_get) instead. For aggregate stats, use [`showings_stats`](/tools/showings/showings_stats). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Search term - matches against address (case-insensitive partial match) | | `status` | enum | No | Filter by status. pending=awaiting confirmation, confirmed=scheduled, completed=done, cancelled=cancelled, no_show=missed (default: all) · One of: `all`, `pending`, `confirmed`, `completed`, `cancelled`, `no_show` | | `showing_type` | enum | No | Filter by showing type (default: all) · One of: `all`, `first_showing`, `follow_up`, `final_walkthrough`, `inspection`, `appraisal` | | `date_from` | string | No | Show showings on or after this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `date_to` | string | No | Show showings on or before this date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `archived` | boolean | No | Include archived showings (default: false) | | `limit` | number | No | Maximum results (default: 50, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "List my confirmed showings between Friday and Sunday this week." - "Pull up any pending showings at 412 Birchwood Ln awaiting confirmation." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # showings_restore > Restore a previously archived showing back to active views. Restore a previously archived showing back to active views. Reverses the effect of [`showings_archive`](/tools/showings/showings_archive). Returns the restored record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `showing_id` | string | Yes | UUID of the showing to restore. Must be currently archived. · Format: UUID | ## Example prompts - "Restore the archived Birchwood Ln showing, the buyers want a second look after all." - "Bring back the Pinehurst Ct showing I archived last week." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # showings_stats > Get aggregate statistics for showings: total count, upcoming count, counts by status, counts by type. Get aggregate statistics for showings: total count, upcoming count, counts by status, counts by type. Use this for dashboard metrics. Does NOT return individual records - use [`showings_list`](/tools/showings/showings_list) for that. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `period` | enum | No | Time period for stats (default: 1_month) · One of: `1_day`, `1_week`, `1_month`, `3_months`, `1_year`, `ytd`, `all` | ## Example prompts - "How many showings did I run this month, broken down by status?" - "Give me my year-to-date showing counts and how many are upcoming." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # showings_update > Update an existing showing's information or status. Update an existing showing's information or status. Only provided fields are updated - omitted fields remain unchanged. Common uses: reschedule (update date/time), status change (pending→confirmed→completed), add feedback/notes. Returns the updated showing record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `showing_id` | string | Yes | UUID of the showing to update (required). Use [`showings_list`](/tools/showings/showings_list) to find. · Format: UUID | | `address` | string | No | Updated property address | | `showing_date` | string | No | Updated showing date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `showing_time` | string | No | Updated showing time in HH:MM format | | `listing_id` | string | No | Updated listing ID · Format: UUID | | `contact_id` | string | No | Updated contact ID · Format: UUID | | `appointment_id` | string | No | Updated appointment ID · Format: UUID | | `showing_type` | enum | No | Updated showing type · One of: `first_showing`, `follow_up`, `final_walkthrough`, `inspection`, `appraisal` | | `access_type` | string | No | Updated access type | | `lockbox_code` | string | No | Updated lockbox code | | `access_notes` | string | No | Updated access notes | | `showing_status` | enum | No | Updated status · One of: `pending`, `confirmed`, `completed`, `cancelled`, `no_show` | | `client_interest_level` | number | No | Client interest level (1-10) · Max: 10 · Min: 1 | | `agent_notes` | string | No | Agent notes about the showing | | `client_feedback` | string | No | Client feedback about the property | | `confirmation_number` | string | No | Showing confirmation number | ## Example prompts - "Reschedule the Garcias showing at Birchwood Ln to Sunday at 3:30pm." - "Mark yesterday's Calloway Dr showing completed and log their interest level at 8." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # Dashboard & stats > At-a-glance counters for your CRM — answers to "how many X do I have?" questions. At-a-glance counters for your CRM — answers to "how many X do I have?" questions. ## Tools (2) | Tool | Type | What it does | | --- | --- | --- | | [`get_dashboard_stats`](/tools/stats/get_dashboard_stats) | Read-only | Get comprehensive statistics for all CRM entities in one call. | | [`get_contact_stats`](/tools/stats/get_contact_stats) | Read-only | Get detailed statistics specifically for contacts including breakdown by contact type. | --- # get_contact_stats > Get detailed statistics specifically for contacts including breakdown by contact type. Get detailed statistics specifically for contacts including breakdown by contact type. Returns: total contacts, new contacts this month, counts by type (vendor, attorney, lender, inspector, escrow_officer, title_rep, etc.). Use this for contact directory health checks or to see distribution of your professional network. More detailed than [`get_dashboard_stats`](/tools/stats/get_dashboard_stats) for contacts. For individual contact details, use [`contacts_list`](/tools/contacts/contacts_list) instead. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "Break down my contact directory by type, lenders, inspectors, title reps, all of it." - "How many new contacts did I add this month, and what's the type distribution?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # get_dashboard_stats > Get comprehensive statistics for all CRM entities in one call. Get comprehensive statistics for all CRM entities in one call. Perfect for dashboard displays and health checks. Returns for each entity type: total count, active count, recent additions. Entities covered: contacts (total, new this month), escrows (by status: active/pending/closed/cancelled), clients (total, active, by type), leads (by status: new/contacted/qualified), listings (by status: active/pending/sold), appointments (today count, this week count). Use entity parameter to filter to specific type, or "all" for complete overview. This is a read-only aggregation — no individual records returned. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `entity` | enum | No | Which entity to get stats for. "all" returns stats for every entity type. Default: all. · One of: `all`, `contacts`, `escrows`, `clients`, `leads`, `listings`, `appointments` | ## Example prompts - "Give me a quick overview of my whole pipeline, leads, listings, escrows, everything." - "How many active escrows and new leads do I have right now?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Tenancies > Manage tenancy records, including delinquency lookups, for the property-management vertical. Manage tenancy records, including delinquency lookups, for the property-management vertical. ## Tools (7) | Tool | Type | What it does | | --- | --- | --- | | [`tenancies_list`](/tools/tenancies/tenancies_list) | Read-only | Search the user's property-managed tenancies. | | [`tenancies_get`](/tools/tenancies/tenancies_get) | Read-only | Get full details of one tenancy by UUID — includes management fee, rent collection state, inspection cadence, linked lease_id and owner_client_id. | | [`tenancies_create`](/tools/tenancies/tenancies_create) | Creates data | Start managing a lease. | | [`tenancies_mark_rent_collected`](/tools/tenancies/tenancies_mark_rent_collected) | Updates data | Stamp rent as collected for a tenancy. | | [`tenancies_record_inspection`](/tools/tenancies/tenancies_record_inspection) | Updates data | Record a property inspection. | | [`tenancies_delinquent`](/tools/tenancies/tenancies_delinquent) | Read-only | List active and vacating tenancies where rent is currently late (rent_current=FALSE). | | [`tenancies_stats`](/tools/tenancies/tenancies_stats) | Read-only | Get aggregate property-management portfolio stats: total tenancies, by_status breakdown, assets_under_management_monthly (sum of monthly_rent from the linked leases of active tenancies — the recurring revenue you're managing), delinquent_count, inspections_due_in_30_days. | --- # tenancies_create > Start managing a lease. Start managing a lease. Requires lease_id (the UUID of an existing lease). Use when taking over management of a signed lease outside the consultation flow — for the common case of converting a signed PM consultation into a tenancy, prefer [`pm_consultations_convert_to_tenancy`](/tools/pm-consultations/pm_consultations_convert_to_tenancy), which atomically signs + creates. Defaults management_fee_pct=10.00, rent_collection_day=1, rent_current=TRUE, status='active'. Returns the created tenancy record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `lease_id` | string | Yes | UUID of the lease to start managing (required) · Format: UUID | | `owner_client_id` | string | No | UUID of the owner client (landlord) who hired the PM · Format: UUID | | `pm_consultation_id` | string | No | UUID of the consultation that led to this tenancy (optional; for audit trail) · Format: UUID | | `management_fee_pct` | number | No | Management fee percentage (default 10.00) · Max: 100 · Min: 0 | | `rent_collection_day` | number | No | Day of month rent is collected (default 1) · Max: 31 · Min: 1 | | `status` | enum | No | Initial status (default: active) · One of: `active`, `vacating`, `vacant`, `terminated` | | `notes` | string | No | Free-text notes on the tenancy (operational details, landlord preferences, etc.) · Max length: 10000 | ## Example prompts - "Start managing the new lease at 219 Dover St with an 8 percent fee." - "Set up management for the Whitfield lease, rent collected on the 5th each month." ## 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. --- # tenancies_delinquent > List active and vacating tenancies where rent is currently late (rent_current=FALSE). List active and vacating tenancies where rent is currently late (rent_current=FALSE). Ordered by last_rent_collected_at ascending (longest-overdue first) with NULLs first (never-collected). This is the primary tool for the "who do I need to chase on rent" question. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "Who is behind on rent across my managed properties right now?" - "Show me the longest-overdue delinquent tenancies first so I can start chasing rent." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # tenancies_get > Get full details of one tenancy by UUID — includes management fee, rent collection state, inspection cadence, linked lease_id and owner_client_id. Get full details of one tenancy by UUID — includes management fee, rent collection state, inspection cadence, linked lease_id and owner_client_id. Use [`tenancies_list`](/tools/tenancies/tenancies_list) first if you don't have the UUID. Returns the complete tenancy record. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `tenancy_id` | string | Yes | UUID of the tenancy · Format: UUID | ## Example prompts - "Pull the full management details on the tenancy at 905 Sycamore Ave." - "When is the next inspection due for the Hendersons tenancy, and what's the fee?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # tenancies_list > Search the user's property-managed tenancies. Search the user's property-managed tenancies. Returns id, lease_id, status (active/vacating/vacant/terminated), rent_current, management_fee_pct, next_inspection_due_at. Use rent_current=false to find delinquent tenancies (or call [`tenancies_delinquent`](/tools/tenancies/tenancies_delinquent) for a dedicated view). Pagination: total_count + offset + limit. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `query` | string | No | Free-text search (reserved) | | `status` | enum | No | Filter by tenancy lifecycle status · One of: `active`, `vacating`, `vacant`, `terminated` | | `owner_client_id` | string | No | Filter to tenancies owned by a specific client (landlord) · Format: UUID | | `rent_current` | boolean | No | Filter by rent-current flag (false = delinquent) | | `limit` | number | No | Maximum results (default: 25, max: 500) · Max: 500 · Min: 1 | | `offset` | number | No | Skip N results for pagination (default: 0) · Min: 0 | ## Example prompts - "List all my active managed tenancies with their management fee percentages." - "Show vacating tenancies in Marcus Bell's rental portfolio." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # tenancies_mark_rent_collected > Stamp rent as collected for a tenancy. Stamp rent as collected for a tenancy. Sets last_rent_collected_at (default: today) and flips rent_current to TRUE. Call this after confirming rent receipt (ACH settlement, check cleared, etc.). ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `tenancy_id` | string | Yes | UUID of the tenancy · Format: UUID | | `collected_at` | string | No | Date rent was collected (default: today) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | ## Example prompts - "Mark June rent collected for the Sycamore Ave tenancy, the ACH settled today." - "The Dover St tenant's check cleared yesterday, stamp their rent as received." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # tenancies_record_inspection > Record a property inspection. Record a property inspection. Stamps last_inspection_at and (optionally) sets the next_inspection_due_at. Inspections are typically on a 6-month cadence for active tenancies. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `tenancy_id` | string | Yes | UUID of the tenancy · Format: UUID | | `inspected_at` | string | No | Date of inspection (default: today) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | | `next_due_at` | string | No | When the next inspection should occur (optional — typically +6 months) (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) | ## Example prompts - "Log today's inspection at 905 Sycamore Ave and set the next one for December." - "Record the June 9 walkthrough for the Dover St tenancy, next due in six months." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # tenancies_stats > Get aggregate property-management portfolio stats: total tenancies, by_status breakdown, assets_under_management_monthly (sum of monthly_rent from the linked leases of active tenancies — the recurring revenue you're managing), delinquent_count, inspections_due_in_30_days. Get aggregate property-management portfolio stats: total tenancies, by_status breakdown, assets_under_management_monthly (sum of monthly_rent from the linked leases of active tenancies — the recurring revenue you're managing), delinquent_count, inspections_due_in_30_days. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "What's my total monthly rent under management and how many doors am I managing?" - "How many tenancies are delinquent, and how many inspections come due in 30 days?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Utilities > Helper lookups used before other operations: verified address lookup and parcel/APN lookup. Helper lookups used before other operations: verified address lookup and parcel/APN lookup. ## Tools (2) | Tool | Type | What it does | | --- | --- | --- | | [`lookup_parcel`](/tools/utility/lookup_parcel) | Read-only | Look up cached parcel/county-tax-assessor data by APN+county or property address. | | [`lookup_address`](/tools/utility/lookup_address) | External lookup | Look up a property address using Google Places API to get structured, verified address data. | --- # lookup_address > Look up a property address using Google Places API to get structured, verified address data. Look up a property address using Google Places API to get structured, verified address data. > [!IMPORTANT] > Use this BEFORE creating escrows or listings to ensure accurate address data. Returns: formatted address, street number, street name, city, state, zip code, county (important for transfer tax calculations), latitude/longitude coordinates (for mapping), and place_id. If the address is ambiguous, returns multiple suggestions — pick the correct one. Common issues: apartment numbers may need manual addition, PO boxes are rejected, new construction may not be found. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `address` | string | Yes | The property address to look up. Be as specific as possible. Examples: "123 Main St, Bakersfield, CA", "456 Oak Ave Unit 12, Los Angeles 90001". Include city and state for best results. · Max length: 200 · Min length: 5 | ## Example prompts - "Verify the exact address and county for 7421 Stockdale Hwy, Bakersfield before I open escrow." - "What county is 88 Calloway Dr in? I need it for transfer tax." ## Safety **External lookup.** A read-only lookup against a service outside ActuallyCare. It may take a few seconds and is subject to that service’s availability. --- # lookup_parcel > Look up cached parcel/county-tax-assessor data by APN+county or property address. Look up cached parcel/county-tax-assessor data by APN+county or property address. Returns assessed value, annual property tax, county, owner name (sanitized for AI use). Cache-only read — does not trigger a paid vendor lookup. Use BEFORE generating a net sheet to enrich seller proceeds estimates with verified tax basis. Returns null if the property has not been previously cached. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `apn` | string | No | Assessor Parcel Number (e.g. "123-456-789"). Pair with `county` for the most precise lookup. · Max length: 50 · Min length: 1 | | `county` | string | No | County name (e.g. "Riverside"). Required when looking up by APN. · Max length: 100 · Min length: 1 | | `address` | string | No | Property address. Used when APN is unknown. Lowercased and whitespace-normalized before lookup. · Max length: 250 · Min length: 5 | | `state` | string | No | 2-letter US state code. Defaults to "CA" if omitted. · Max length: 2 · Min length: 2 | ## Example prompts - "Look up the assessed value and annual property tax for 412 Birchwood Ln." - "Check cached assessor data for APN 412-031-022 in Kern County before I build the net sheet." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Verticals & roles > Read-only discovery of platform verticals and role definitions. Read-only discovery of platform verticals and role definitions. ## Tools (4) | Tool | Type | What it does | | --- | --- | --- | | [`vertical_schema_get`](/tools/verticals/vertical_schema_get) | Read-only | Get the metadata schema for a specific vertical and entity type (deal, lead, client, appointment). | | [`verticals_list`](/tools/verticals/verticals_list) | Read-only | List all industry verticals available in the ActuallyCare platform. | | [`roles_list`](/tools/verticals/roles_list) | Read-only | List all user roles in the platform role registry. | | [`role_lookup`](/tools/verticals/role_lookup) | Read-only | Get full details about a specific user role by its key. | --- # role_lookup > Get full details about a specific user role by its key. Get full details about a specific user role by its key. Returns the role's vertical mapping, scope level, description, and whether it allows login. Use this to understand what a specific role key means and what vertical/authorization tier it belongs to. Works for both active and legacy (deprecated) roles. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `role_key` | string | Yes | The role key to look up (e.g., "broker", "plumber", "home_inspector", "transaction_coordinator") | ## Example prompts - "What exactly does the transaction coordinator role allow, and what scope level is it?" - "Is the plumber role loginable, and what vertical is it mapped to?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # roles_list > List all user roles in the platform role registry. List all user roles in the platform role registry. Use to understand what a role can do before assigning it, or to enumerate the roles available in a vertical. Each role maps to exactly one vertical and has a scope_level (admin, brokerage, team, standard) that determines its authorization tier. Filterable by vertical key (e.g., "inspection" returns 16 roles) or scope_level (e.g., "brokerage" returns broker-level roles). Returns role key, vertical_key, vertical_label, label, description, scope_level, and is_loginable. There are roughly 80 active roles across 12 verticals. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `vertical` | string | No | Filter by vertical key (e.g., "real_estate", "inspection", "home_services", "lending"). Leave empty for all roles. | | `scope_level` | enum | No | Filter by scope level. "admin" = full system access, "brokerage" = brokerage-wide, "team" = team-wide, "standard" = own data. · One of: `admin`, `brokerage`, `team`, `standard` | ## Example prompts - "List all brokerage-level roles across the platform." - "What roles exist in the inspection vertical?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # vertical_schema_get > Get the metadata schema for a specific vertical and entity type (deal, lead, client, appointment). Get the metadata schema for a specific vertical and entity type (deal, lead, client, appointment). Returns field definitions with types, labels, validation rules, and select options. Use this to understand what structured metadata fields are available for a vertical before creating or updating deals. Example: get lending deal schema to see loan_type, interest_rate, ltv_ratio fields. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `vertical_key` | string | Yes | Vertical key (e.g., lending, inspection, home_services) | | `entity_type` | enum | Yes | Entity type to get schema for · One of: `deal`, `lead`, `client`, `appointment` | ## Example prompts - "What metadata fields are available on lending deals, like loan type and rate?" - "Show me the structured fields for inspection appointments before I create one." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # verticals_list > List all industry verticals available in the ActuallyCare platform. List all industry verticals available in the ActuallyCare platform. Each vertical represents an industry segment (real_estate, lending, inspection, home_services, etc.) with its own pipeline labels. Returns vertical key, label, description, icon, pipeline_labels (entity naming by stage), and role_count. Use this to understand what industries the platform supports and how each pipeline stage is labeled per vertical. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "Which industry verticals does the platform support, and how are their pipelines labeled?" - "List every vertical with its pipeline stage names and role counts." ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # Websites > Agent personal website edit-publish-revert cycle, with Fair Housing, DRE, and IDX guardrails enforced server-side. Agent personal website edit-publish-revert cycle, with Fair Housing, DRE, and IDX guardrails enforced server-side. ## Tools (4) | Tool | Type | What it does | | --- | --- | --- | | [`website_get`](/tools/websites/website_get) | Read-only | Get the current user's personal website status and settings. | | [`website_edit`](/tools/websites/website_edit) | Creates data + external action | Edit the agent's personal website using natural language. | | [`website_publish`](/tools/websites/website_publish) | Updates data | Publish the current draft of the agent's website to make it live. | | [`website_revert`](/tools/websites/website_revert) | Irreversible | Revert the agent's website draft to the last published version. | --- # website_edit > Edit the agent's personal website using natural language. Edit the agent's personal website using natural language. Describe what you want to change (colors, layout, text, sections) and the AI will update the HTML/CSS in real time. Examples: "Change the hero background to dark blue", "Add a section about my specialties", "Make the contact form more prominent". The edit is applied to the draft — use [`website_publish`](/tools/websites/website_publish) to make it live. Guardrails enforce Fair Housing, DRE, and IDX compliance automatically. Returns the updated HTML, diff summary, and any guardrail flags. ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `prompt` | string | Yes | Natural language description of the edit to make. Be specific about what to change and how. · Max length: 2000 | ## Example prompts - "Change my website hero background to dark blue and make the contact form bigger." - "Add a section to my site about my Bakersfield luxury listing specialty." ## Safety **Creates data + external action.** Creates a record and triggers an action in a connected external service. --- # website_get > Get the current user's personal website status and settings. Get the current user's personal website status and settings. Returns: id, templateId, status (draft/published/suspended), subdomain, metaTitle, metaDescription, approvalRequired, approvalStatus, publishedAt, createdAt. Use this to check if the agent has a website and its current state before performing other website operations. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "Is my personal website published yet, and what subdomain is it on?" - "Check my website status, did the brokerage approve it for publishing?" ## Safety **Read-only.** This tool never changes your data — it only looks things up. Safe to run anytime. --- # website_publish > Publish the current draft of the agent's website to make it live. Publish the current draft of the agent's website to make it live. The website will be accessible at username.actuallycare.com. Only works if there is draft content to publish. If the brokerage requires approval, the website must be approved first before publishing. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "My draft looks good, push my website live at my subdomain." - "Publish the latest draft of my agent site so visitors see the new bio." ## Safety **Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back. --- # website_revert > Revert the agent's website draft to the last published version. Revert the agent's website draft to the last published version. Use this to undo all draft changes and restore the live version. Only works if there is a published version to revert to. ## Parameters _This tool takes no parameters — just ask._ ## Example prompts - "Scrap my draft changes and roll my website back to the live version." - "Undo everything in my site draft, but double-check with me before reverting." ## Safety **Irreversible.** This action cannot be undone. Claude should always confirm with you before running it.