list_follow_up_tasks
List follow-up tasks — reminders for a person to get back to a contact. Read-only, ordered by due time so overdue work comes first. A follow-up sends nothing by itself. Scopes: mine is the open work assigned to the key's owner and needs a personal key; unassigned is unowned open work; team is all open work; completed is closed history. unassigned, team and completed reach past the caller's own tasks ONLY for an owner or admin of the application, or a workspace API key. For any other personal key unassigned and team return the same as mine, and completed returns only their own closed tasks — the result's scope.narrowedToOwn is true when that happened. Without a scope a personal key reads mine and a workspace key reads team. completionReason tells a person closing a task apart from the platform closing it (customer_replied, expired_unanswered).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number. Defaults to 1. | |
| limit | No | Tasks per page, 1-100. Defaults to 20. | |
| scope | No | Whose work to list. `mine` requires a personal API key; `unassigned`, `team` and `completed` widen past the caller's own tasks only for an owner, an admin or a workspace key. | |
| origin | No | Who created it: a person, the AI analysis, or a deterministic rule. | |
| search | No | Substring match on the contact's name, username, or platform id. | |
| timing | No | Narrow by when the task is due. Omit for all open work. | |
| applicationId | No | Application (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id. |