Lofty

Stop the emails of a lead's saved searches (property alerts / market snapshots) without deleting them - either the ones in 'ids', or every one of the kinds in 'categories'. resume_saved_searches switches them back on. List a lead's saved searches and their ids with search_leads (scope="saved_searches", lead_id).

pause_saved_searches

Read a previously generated call summary, or list lead analysis tasks. To generate a new one, use generate_lead_insight.

search_lead_insights

Every read-only piece of team and organization configuration: your own profile (kind=members.me - call this once at the start of a session, every 'my tasks' or 'my leads' query depends on knowing who is asking), team members, tags, custom field definitions, pipelines, ponds, vendors, organization info, permission profiles, and lead routing rules and roles. A lead's own system event log is search_lead_activities (channel=system_log), not this tool - it's per-lead data, not team/organization configuration.

search_team_config

Switch a lead's paused saved searches (property alerts / market snapshots) back on; each resumes at the cadence it ran at before it was paused. List a lead's saved searches and their ids with search_leads (scope="saved_searches", lead_id).

resume_saved_searches

Everything that happened on a lead, or across every lead one agent touched: calls, texts, emails, notes, manual log entries, system events (stage changes, assignment/routing, subscriptions, smart-plan tasks), and the unified activity timeline. Writing a note or manual log entry is manage_leads (actions add_note/update_note/delete_note/add_manual_log/delete_manual_log) - this tool is read-only.

search_lead_activities

Filter leads by status, source, tag, owner or custom field; fetch one or many by id; read the property searches a lead has saved (scope="saved_searches" with lead_id). Set group_by (optionally with metric) instead of paging through records yourself when the question is a count or sum, not a list - e.g. "how many leads per source last month". Notes, manual logs, calls, texts, emails and the activity timeline live in search_lead_activities, not here; lead writes live in manage_leads, saved-search writes in create_saved_search, update_saved_search, delete_saved_search, pause_saved_searches and resume_saved_searches.

search_leads

Published listings by agent or office, or the published feed. Read-only at this layer - listing creation and maintenance isn't part of this API surface. scope=agent/office returns JSON; scope=published returns the feed's own XML verbatim (CHIME-70594), not JSON - that endpoint is an XML-only syndication feed, not a per-team JSON search.

search_listings

Tasks and calendar events - list, fetch one by id, the caller's own tasks across every lead, or open meeting slots. kind=showing switches to property showings (list, fetch one, or its feedback). Writes live in manage_tasks.

search_tasks

The AI working-lead pool, membership and mute status, quota, current agent, settings, and plan tasks for a lead.

search_sales_agent

Search transactions globally or for one lead, fetch one or many by id, read a transaction's property address, or the team's transaction custom field definitions. Set group_by (optionally with metric) for a count/sum instead of a record list.

search_transactions

Send SMS or email to one lead from the authenticated agent. Always confirms - the recipient and the full rendered body are shown before sending, and this cannot be undone once sent.

send_message

Register a new webhook subscription, or remove an existing one. Both change what an external system is told about this account - confirm with the user before calling either.

manage_webhooks

Change the name, schedule, filters, recipients or other settings of one or more of a lead's saved searches (property alerts / market snapshots). Setting fields.alertFrequency to NEVER pauses one, like pause_saved_searches. List a lead's saved searches and their ids with search_leads (scope="saved_searches", lead_id).

update_saved_search

Add a custom field, update lead routing rules, add or update an office, update company info, or create/tag/deactivate/reactivate an agent account. Note the one place Lofty's REST API inverts convention: PUT on the office endpoint adds a new office, POST updates an existing one - this tool hides that behind add_office/update_office so the HTTP verb is never something you need to know.

manage_team_config