manage_tasks

WRITE · 9 operations · may change data

Create, update, delete, complete and un-complete tasks and calendar events. There is no top-level mode to pick — a single fields.type decides what’s created.

manage_tasks({
  action: "create" | "update" | "delete" | "complete" | "uncomplete" | "cancel" | "add_feedback",
  kind?, ids?, fields?, confirm_token?
})

cancel and add_feedback exist only for kind: "showing" (below); the other five are the task/event actions. delete is an Always-confirm action: the first call returns needsConfirmation with a confirm_token; replay the identical call with that token to actually delete. ids (for update/delete/complete/uncomplete) must be the composite ids search_tasks itself returns (e.g. "12345-task"), not a bare number. fields.type (create only) decides what’s created — a different enum from anything at the top level of this tool:

`fields.type`	Required `fields`	Notes
`Other` / `Call` / `Email` / `Text`	`content`, `leadId`, `type`, `assignedRole` (`Agent`/`Assistant`), `endAt`	`endAt` is the deadline, not a range end. Optional: `startAt` (not used), `timeZoneCode`.
`Appointment`	`content`, `leadId`, `startAt`, `endAt`	Both ISO 8601 with a UTC offset, e.g. `2026-03-01T15:00:00-08:00`. Optional: `timeZoneCode`, `address`.

There is no title/subject/dueDate field — content and endAt are it. A missing required field is rejected before the call reaches the backend, naming exactly which one.

Showings

kind: "showing" manages property showings on a lead through /v2.0/showings. Only showings this partner created can be updated, cancelled or given feedback — showings booked inside Lofty are read-only.

Call	Resolves to	Confirms?
`{kind:"showing", action:"create", fields}`	`POST /v2.0/showings` — `fields` needs `leadId`, `startAt`, `endAt` (ISO 8601 with offset) and `listing` (`{listingId}` / `{mlsOrgId, mlsListingId}` / `{address}`); optional `status` (default `scheduled`), `note`, `externalId` (idempotency key)	No
`{kind:"showing", action:"update", ids, fields}`	`PATCH /v2.0/showings/{showingId}` per id — any of `startAt`, `endAt`, `status`, `note`	No
`{kind:"showing", action:"cancel", ids}`	`POST /v2.0/showings/{showingId}/cancel` per id	Always
`{kind:"showing", action:"add_feedback", ids, fields}`	`POST /v2.0/showings/{showingId}/feedback` per id — one of `content` or `payload`, plus optional `authorType` (`buyer_agent` / `lead` / `listing_agent` / `partner`), `authorName`, `externalId`	No

ids are plain showing ids (as returned by search_tasks with kind: "showing"), not the composite task ids.

Get Started

Read Tools

Write Tools

Guides

Showings

​Showings

Showings