List tasks
well_list_tasksList the tasks of the workspace, most important first, at most 50: each with the same fields as well_get_task, without the browser detail. Narrow it by status and by priority (each one value or a list), by created_by (me, teammate or well), by task_kind (browser-task for the browser tasks), by assignee and by due_date. assigned_to_id with due_date is one member's day. Each task carries slot: the calendar event booked for it, with its own start and end, or null when the job has no slot yet or its slot is private to another member. Read a job's time from slot only; a task carries no time of its own. When the answer carries slots_unavailable, the calendar could not be read at all: the times are then unknown, and never say a job is unbooked. Each row also carries created_by_kind, completion_note and run (where a browser task stands, for its own person only). total is the count of every task that matches. It changes nothing. A guest lists only the tasks assigned to them. When the list is empty, tell the person: Nothing needs you right now.
When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many tasks to return, at most 50. Default 20. | |
| status | No | Only the tasks in this status, or in any of a list of statuses. Leave it out for every status. | |
| due_date | No | Only the tasks due on this exact day, "YYYY-MM-DD". Send it with assigned_to_id for one member's day. | |
| priority | No | Only the tasks of this priority, or of any of a list of priorities. Leave it out for every priority. | |
| task_kind | No | Only the tasks of this kind, for example "browser-task" for the browser tasks. | |
| created_by | No | Only the tasks made by these: me (the person), teammate (another person) or well (Well). | |
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which. | |
| assigned_to_id | No | Only the tasks assigned to this person. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| tasks | No | ||
| total | No | ||
| success | Yes | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| slots_unavailable | No | ||
| resolved_workspace | No | The workspace that answered, when the caller named none and the token authorizes several. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. |