MCPTool reference
Contact Tasks
BlueSuite MCP tools for contact tasks
See connection and authentication and workflow rules before calling these tools.
Related REST API and behavior.
list_contact_tasks
List the follow-up tasks and reminders on a client, things like "call back Thursday" or "annual service due". Filter by status to see what is still outstanding.
Parameters
| Field | Type / accepted values | Required | Details |
|---|---|---|---|
contact_id | integer | Yes | Contact ID whose tasks to list. |
status | array of "open", "completed", "overdue" | No | Filter by one or more statuses: open, completed, overdue. |
page | integer | No | Page number (default: 1) |
per_page | integer | No | Results per page minimum: 1. maximum: 100. |
Result
| Field | Type / accepted values | Required | Details |
|---|---|---|---|
data | array of object | Yes | The matching records for this page. |
pagination | object | No | How many more pages of results exist. Absent when the API returned an unpaged result. |
pagination.page | integer | When parent supplied | Current page number, 1-based. |
pagination.per_page | integer | When parent supplied | Number of results per page. |
pagination.total_pages | integer | When parent supplied | Total number of pages available. |
create_contact_task
Add a follow-up task or reminder to a client. Use this for anything the user wants to remember about a specific client that is not itself billable work, "follow up next week", "chase the deposit", "annual service due in March". For work that gets done and paid for, create a job instead.
Parameters
| Field | Type / accepted values | Required | Details |
|---|---|---|---|
contact_id | integer | Yes | Contact the task belongs to. |
title | string | Yes | Short title, e.g. "Call about deck quote". |
description | string | No | Any extra detail. |
due_date | string | No | When it is due, as an ISO timestamp. Reminders fire relative to this, so include a time, "Thursday" alone is not enough. Required for a recurring task. |
assignee_id | string | No | UUID of the team member responsible. Use list_users to resolve a name. Format: uuid. |
reminders_enabled | boolean | No | Whether the assignee is notified as the due date approaches. Defaults to FALSE, so a task created without this is a silent to-do that nobody is nudged about. Turn it on when the user says "remind me". |
recurrence_type | "single", "recurring" | No | Set to 'recurring' for a reminder that repeats (a yearly service check, a monthly courtesy call). Default: 'single'. |
repeat_frequency | integer | No | Interval, used when repeat_frequency_unit is 'custom'. |
repeat_frequency_unit | "daily", "weekly", "monthly", "yearly", "custom", "forever", "occurrences" | No | How often it repeats: daily, weekly, monthly, yearly, or custom. Default: weekly. |
repeat_frequency_unit_custom | "daily", "weekly", "monthly", "yearly", "custom", "forever", "occurrences" | No | Unit the custom interval counts in. Only used with repeat_frequency_unit='custom'. |
repeat_frequency_schedule | object | No | Which days a custom weekly or monthly pattern lands on. Required for those. |
repeat_frequency_schedule.days | array of JSON value | When parent supplied | 1-7 for weekdays, 1-31 for days of the month. |
repeat_frequency_schedule.type | "weekDays", "monthWeekDays", "monthDays" | When parent supplied | |
repeat_duration | JSON value | No | How long it repeats. With repeat_duration_unit='occurrences' this is a count. Required unless it repeats forever. |
repeat_duration_unit | "daily", "weekly", "monthly", "yearly", "custom", "forever", "occurrences" | No | How it ends: 'forever', 'occurrences', or a time unit. Default: forever. |
Result
| Field | Type / accepted values | Required | Details |
|---|---|---|---|
data | object or null | Yes | The affected record, or the result of the operation. Null when nothing matched. |
update_contact_task
Edit a follow-up task. To mark one done, use complete_contact_task instead, for a repeating reminder, that completes just the one occurrence rather than touching the series.
Parameters
| Field | Type / accepted values | Required | Details |
|---|---|---|---|
contact_id | integer | Yes | Contact the task belongs to. |
task_id | JSON value | Yes | Task ID. |
title | string | No | New title. |
description | string | No | New description. |
due_date | string | No | New due date as an ISO timestamp. |
assignee_id | string | No | UUID of the team member responsible. Use list_users to resolve names. Format: uuid. |
reminders_enabled | boolean | No | Whether the assignee is notified as the due date approaches. Defaults to FALSE, so a task created without this is a silent to-do that nobody is nudged about. Turn it on when the user says "remind me". |
update_scope | "single", "all", "recreate" | No | For a repeating reminder: 'single' changes only this one, 'all' applies to future ones too, 'recreate' rebuilds the upcoming series after a pattern change. Ask which the user means. Default: single. |
recurrence_type | "single", "recurring" | No | Set to 'recurring' for a reminder that repeats (a yearly service check, a monthly courtesy call). Default: 'single'. |
repeat_frequency | integer | No | Interval, used when repeat_frequency_unit is 'custom'. |
repeat_frequency_unit | "daily", "weekly", "monthly", "yearly", "custom", "forever", "occurrences" | No | How often it repeats: daily, weekly, monthly, yearly, or custom. Default: weekly. |
repeat_frequency_unit_custom | "daily", "weekly", "monthly", "yearly", "custom", "forever", "occurrences" | No | Unit the custom interval counts in. Only used with repeat_frequency_unit='custom'. |
repeat_frequency_schedule | object | No | Which days a custom weekly or monthly pattern lands on. Required for those. |
repeat_frequency_schedule.days | array of JSON value | When parent supplied | 1-7 for weekdays, 1-31 for days of the month. |
repeat_frequency_schedule.type | "weekDays", "monthWeekDays", "monthDays" | When parent supplied | |
repeat_duration | JSON value | No | How long it repeats. With repeat_duration_unit='occurrences' this is a count. Required unless it repeats forever. |
repeat_duration_unit | "daily", "weekly", "monthly", "yearly", "custom", "forever", "occurrences" | No | How it ends: 'forever', 'occurrences', or a time unit. Default: forever. |
Result
| Field | Type / accepted values | Required | Details |
|---|---|---|---|
data | object or null | Yes | The affected record, or the result of the operation. Null when nothing matched. |
complete_contact_task
Mark a follow-up task done, or reopen one. For a repeating reminder this affects only the single occurrence, leaving the rest of the series in place.
Parameters
| Field | Type / accepted values | Required | Details |
|---|---|---|---|
contact_id | integer | Yes | Contact the task belongs to. |
task_id | JSON value | Yes | Task ID. |
status | "open", "completed", "overdue" | Yes | completed to mark it done, open to reopen it, overdue to flag it. |
Result
| Field | Type / accepted values | Required | Details |
|---|---|---|---|
data | object or null | Yes | The affected record, or the result of the operation. Null when nothing matched. |
delete_contact_task
Delete a follow-up task. To record that it was done rather than remove it, use complete_contact_task, deleting loses the history.
Parameters
| Field | Type / accepted values | Required | Details |
|---|---|---|---|
contact_id | integer | Yes | Contact the task belongs to. |
task_id | JSON value | Yes | Task ID. |
Result
| Field | Type / accepted values | Required | Details |
|---|---|---|---|
data | object or null | Yes | The affected record, or the result of the operation. Null when nothing matched. |
The downloadable tool schemas include the full input and output contracts. Tables describe schema-level required fields; cross-field rules still apply.