> ## Documentation Index
> Fetch the complete documentation index at: https://developer.lofty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# search_tasks

> Tasks and calendar events — list, fetch by id, "my tasks" across every lead, and available meeting slots.

> [!NOTE]
>
> **READ** · 6 operations · never changes data

Tasks and calendar events — list, fetch by id, "my tasks" across every lead, and available meeting slots. There is no separate mode to pick between to-dos and appointments; both resolve through the same search.

```js theme={null}
search_tasks({
  kind?, lead_id?, id?, status?, feedback?, my_tasks?, available_slots?, filters?, limit?, cursor?
})
```

`lead_id` is an optional filter — omit it for a search across every lead. `id` fetches one record instead of searching.

`filters` holds whatever extra query parameters the resolved endpoint accepts:

| Mode | `filters` holds |
| - | - |
| A search or `my_tasks` | `startTime`, `endTime`, `includeFinished`, `page`, `pageSize`, `sort`. A wide default time window is used when neither `startTime` nor `endTime` is supplied. |
| `available_slots` | `startTime`, `endTime` |

`lead_id` is not used at all for `my_tasks`/`available_slots`.

> [!WARNING]
>
> `assignee`, `completed` and `due_between` are **not** real parameters, despite looking like
> reasonable filters — no task search variant accepts them. Passing any of them returns a clear
> error rather than being silently ignored. Fetch by `lead_id` (or `my_tasks`) and filter
> client-side instead.

> [!NOTE]
>
> `id` accepts either the composite id this tool itself returns (e.g. `"12345-task"`) or a bare
> numeric id — a bare id is tried against both tasks and appointments before giving up.

## Showings

`kind: "showing"` switches the tool to property showings on a lead — the ones partners push through `/v2.0/showings` and the ones booked inside Lofty.

| Call | Resolves to |
| - | - |
| `{kind:"showing", lead_id?, status?, filters?}` | `GET /v2.0/showings` — `status` is one of `requested`, `scheduled`, `in_progress`, `completed`, `denied`, `expired`, `cancelled`; `filters` may carry `startAt`, `endAt` (ISO 8601) and `externalId` |
| `{kind:"showing", id}` | `GET /v2.0/showings/{showingId}` |
| `{kind:"showing", id, feedback:true}` | `GET /v2.0/showings/{showingId}/feedback` |

Writes (create/update/complete/delete) live in [`manage_tasks`](https://developer.lofty.com/mcp/tools/manage-tasks).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.