Profit.co

Creates a key result in Profit.co under the given objective. Parameters are normally supplied after the key result preview flow (get_key_result_creation_preview), when the user is ready to create. The connector selects default key result settings from the firm configuration: Percentage Tracked type, Every Friday check-in frequency, Not Started status, and the current period. Returns created key result details for display. Keep internal identifiers such as ownerId, ownerTypeId, and objectiveId out of user-facing text. CRITICAL — confirmation required: Call only after (1) the user confirmed via the in-chat confirmation card/button when it is visible, OR (2) the card did not render or was skipped and the user sent an explicit confirmation in chat after reviewing the preview. Never call immediately after a preview tool. Never infer confirmation from the original create/update/submit request alone. --- Creates a key result in Profit.co under the selected objective. Use this tool after `get_key_result_creation_preview` has returned a confirmation-ready payload (for example, `pending_user_confirmation`) and the user has confirmed. CRITICAL — confirmation required: Call only after (1) the user confirmed via the in-chat confirmation card/button when it is visible, OR (2) the card did not render or was skipped and the user sent an explicit confirmation in chat after reviewing the preview. Never call immediately after a preview tool. Never infer confirmation from the original create/update/submit request alone. The connector applies default firm settings for new key results, including: - Percentage Tracked key result type, - Every Friday check-in frequency, - Not Started status. Do not expose internal identifiers (for example, ownerId, ownerTypeId, or objectiveId) in user-facing text.

Creates a new OKR objective in Profit.co after the user has confirmed the objective preview. This tool is used after get_objective_creation_preview returns a confirmation-ready payload and the user confirms. CRITICAL — confirmation required: Call only after (1) the user confirmed via the in-chat confirmation card/button when it is visible, OR (2) the card did not render or was skipped and the user sent an explicit confirmation in chat after reviewing the preview. Never call immediately after a preview tool. Never infer confirmation from the original create/update/submit request alone. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. After create_okr_objective succeeds, do not call get_my_okrs unless the user explicitly asked to list or view their OKRs in that message. --- Creates a new objective in Profit.co after the user confirms the objective preview. This tool is part of the objective confirmation flow: - Use `get_objective_creation_preview` to gather level, period, and objective details. - After the user confirms (confirmation card when visible, or explicit chat confirmation when the card did not render), call this tool. CRITICAL — confirmation required: Call only after (1) the user confirmed via the in-chat confirmation card/button when it is visible, OR (2) the card did not render or was skipped and the user sent an explicit confirmation in chat after reviewing the preview. Never call immediately after a preview tool. Never infer confirmation from the original create/update/submit request alone. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. After create_okr_objective succeeds, do not call get_my_okrs unless the user explicitly asked to list or view their OKRs in that message. Keep internal identifiers (for example, ownerId and ownerTypeId) out of user-facing text.

Creates a new task in Profit.co after the required task details have been provided and confirmed. CRITICAL — confirmation required: Call only after (1) the user confirmed via the in-chat confirmation card/button when it is visible, OR (2) the card did not render or was skipped and the user sent an explicit confirmation in chat after reviewing the preview. Never call immediately after a preview tool. Never infer confirmation from the original create/update/submit request alone. --- Creates a new task in Profit.co. Use this tool after `get_task_creation_preview` has returned a confirmation-ready payload and the user has confirmed task creation. CRITICAL — confirmation required: Call only after (1) the user confirmed via the in-chat confirmation card/button when it is visible, OR (2) the card did not render or was skipped and the user sent an explicit confirmation in chat after reviewing the preview. Never call immediately after a preview tool. Never infer confirmation from the original create/update/submit request alone. Typical flow: 1) Call `get_task_creation_preview` first to prepare and validate task details. 2) Present the preview/confirmation UI. 3) After user confirmation, call `create_task` with values from structured content. Expected parameters (from preview structured content): - `subject` (required) - `dueDate` (optional) - `statusName` (optional; defaults to `Not Started` when omitted) - `priorityName` (optional; defaults to `High` when omitted) - `assigneeEmployeeId` (optional) - `assigneeName` (optional) - `noAssignee` is not used in this flow. Behavior notes: - A valid user session is required. - `subject` is required and sanitized before creation. - Assignee is validated server-side against Profit.co assignable employees; omit assignee fields to use the session user, or pass only values from preview structuredContent. - Return includes created task details (for example, task name and assignee) or an error response.

Prepares and previews the data required to submit a check-in in Profit.co. Use this tool when the user wants to view available key results for check-in, list available check-in statuses, or prepare a check-in before submission. It retrieves relevant check-in data and validates provided inputs such as the key result, check-in value, status, and comment. When sufficient information is available, the tool returns a preview of the check-in and may present a confirmation interface. This tool does not create or modify any data. When this returns status `pending_user_confirmation`: if the confirmation card renders, wait for the user to click Confirm before calling the matching create/submit/update tool. Do not ask the user to type yes/confirm/proceed in chat when the card is visible—the card is the only confirmation UI needed. If the confirmation card/UI is not visible or was skipped: STOP. Show the preview to the user and ask them to confirm explicitly in chat (for example: yes, confirm, proceed). Wait for that reply. Only then call the matching create/submit/update tool with values from structuredContent. Do NOT call that tool in the same turn as the preview. Do NOT treat the user's original request as confirmation. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. --- Prepares and previews check-in data from Profit.co. This tool is read-only and does not create or update data. Use this tool when the user wants to: - list key results available for check-in, - list check-in statuses, - prepare a check-in with key result, value, optional status, and optional comment. Behavior: - Retrieves real check-in data from Profit.co (key results, sub-key results, and statuses). - If `listStatusesOnly` is true, returns available check-in statuses. - Can filter by `objectiveName` when the user asks for key results under a specific objective. - Validates provided check-in inputs and, when complete, returns a confirmation-ready preview (`pending_user_confirmation`). Confirmation flow (required before `submit_checkin`): - When preview is returned, direct the user to confirm via the confirmation card when it renders. - If the confirmation card/UI is not visible or was skipped: STOP. Show the preview to the user and ask them to confirm explicitly in chat (for example: yes, confirm, proceed). Wait for that reply. Only then call the matching create/submit/update tool with values from structuredContent. Do NOT call that tool in the same turn as the preview. Do NOT treat the user's original request as confirmation. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. - Do not report success until `submit_checkin` succeeds. Do not expose internal identifiers (for example, ownerId, ownerTypeId, keyResultId, or objectiveId) in user-facing text.

Prepares and previews the data required to create a key result in Profit.co. Use this tool when the user wants to add a key result but has not yet confirmed creation. It retrieves available levels, objectives, and related context based on user input. When sufficient information is available, the tool returns a preview of the key result and may present a confirmation interface. This tool does not create or modify any data. When this returns status `pending_user_confirmation`: if the confirmation card renders, wait for the user to click Confirm before calling the matching create/submit/update tool. Do not ask the user to type yes/confirm/proceed in chat when the card is visible—the card is the only confirmation UI needed. If the confirmation card/UI is not visible or was skipped: STOP. Show the preview to the user and ask them to confirm explicitly in chat (for example: yes, confirm, proceed). Wait for that reply. Only then call the matching create/submit/update tool with values from structuredContent. Do NOT call that tool in the same turn as the preview. Do NOT treat the user's original request as confirmation. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. --- Prepares data and preview details for key result creation in Profit.co. This tool is read-only and does not create or modify data. Use this tool when the user wants to add a key result, create a key result, or add a key result to an objective. Typical flow: 1) Initial request: call with no parameters (or level only) to present available options. 2) If the user asks to list objectives across all levels: call with `listAllObjectives: true` (without level). 3) If the user selects a level: call with `level` (and `departmentId` or `departmentName` when applicable) to retrieve objectives for that level. 4) When objective and key result name are available: call with objective and owner context to return a preview for confirmation. Confirmation (required before `create_okr_key_result`): - If the confirmation card renders: wait for Confirm on the card. - If the confirmation card/UI is not visible or was skipped: STOP. Show the preview to the user and ask them to confirm explicitly in chat (for example: yes, confirm, proceed). Wait for that reply. Only then call the matching create/submit/update tool with values from structuredContent. Do NOT call that tool in the same turn as the preview. Do NOT treat the user's original request as confirmation. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. Do not expose internal identifiers (for example, ownerId, ownerTypeId, or objectiveId) in user-facing text.

Lists the signed-in user's objectives and key results from Profit.co, including sub-key results, for the individual OKR level only. Read-only. No parameters. Use when the user wants to view or list their personal OKRs (for example, phrases like "my OKRs", "show my objectives and key results", or similar intent for their own individual OKRs). Do not call this tool automatically after creating an objective, key result, or task unless the user asked to see their OKRs. This tool does not aggregate corporate- or department-level OKR trees. If the user asks for organization-wide or all-level OKR views, explain that this listing is limited to the individual level, or guide them in Profit.co for other scopes. --- Use this tool when the user asks to see their own OKRs, objectives, key results, goals, or progress at the individual level. Examples include: - "list my OKRs" - "show my objectives" - "list my objectives and key result" Do not use this tool for organization-wide, team, department, corporate, or other users' OKRs. Do not use this tool for create/update actions (objective creation, key result creation, check-ins, task updates, pending actions). Do not call automatically after create_okr_objective unless the user asked to view their OKRs. Returns only the signed-in user's individual-level OKRs from Profit.co. Read-only. No parameters.

Collects Profit.co data needed before creating an objective: available levels, current period, and owner context. Does not create an objective. Call with no arguments to show level options when the user wants to create an objective but has not chosen a level or title yet. Include level (individual, corporate, or department, with department fields when applicable) once the user has stated it. Include objectiveName only as the exact title the user provided. When level and objectiveName are both available, the tool returns a preview and drives the in-chat confirmation UI when available. Objective creation is completed by create_okr_objective only after user confirmation—not by inferring create_okr_objective from this tool alone. When this returns status `pending_user_confirmation`: if the confirmation card renders, wait for the user to click Confirm before calling the matching create/submit/update tool. Do not ask the user to type yes/confirm/proceed in chat when the card is visible—the card is the only confirmation UI needed. If the confirmation card/UI is not visible or was skipped: STOP. Show the preview to the user and ask them to confirm explicitly in chat (for example: yes, confirm, proceed). Wait for that reply. Only then call the matching create/submit/update tool with values from structuredContent. Do NOT call that tool in the same turn as the preview. Do NOT treat the user's original request as confirmation. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. Do not show internal identifiers such as ownerId or ownerTypeId to the user. --- Collects Profit.co data required before creating an objective. This tool is read-only and does not create or modify data. It can return: - available level options, - current period information, - and an objective preview for user confirmation. Use this tool when the user wants to create an objective and details are still being gathered or reviewed. Rules: - Level must come from the user. Do not assume or default a level. - Objective name must come from the user's exact intent. Do not invent or rewrite it. - If level is missing, call without level so the tool can present options. - If objective name is missing, call without objectiveName so the tool can request it. - After level and objectiveName are provided, this tool returns a preview and confirmation UI when the client supports it. - Creation is completed through `create_okr_objective` only after user confirmation. - Do not expose internal identifiers such as ownerId or ownerTypeId in user-facing text. Confirmation (required before `create_okr_objective`): - If the confirmation card renders: wait for the user to click Confirm; do not call `create_okr_objective` yourself in that turn. - If the user types confirm/yes/proceed in chat (Cursor and other clients without the card): call `create_okr_objective` only—do not call this preview tool again. - If the confirmation card/UI is not visible or was skipped: STOP. Show the preview to the user and ask them to confirm explicitly in chat (for example: yes, confirm, proceed). Wait for that reply. Only then call the matching create/submit/update tool with values from structuredContent. Do NOT call that tool in the same turn as the preview. Do NOT treat the user's original request as confirmation. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. Typical flow: 1) User asks to create an objective -> call with no parameters. 2) User provides level and/or objective name -> call again with only the fields the user provided. 3) When both are available -> present preview and wait for user confirmation.

Prepares and previews the data required to create a task in Profit.co. Use this tool when the user wants to create a task but has not yet confirmed creation. It validates provided task details such as the subject, due date, status, and priority, and returns a preview of the task for confirmation. When sufficient information is available, the tool may present a confirmation interface. This tool does not create or modify any data. When this returns status `pending_user_confirmation`: if the confirmation card renders, wait for the user to click Confirm before calling the matching create/submit/update tool. Do not ask the user to type yes/confirm/proceed in chat when the card is visible—the card is the only confirmation UI needed. If the confirmation card/UI is not visible or was skipped: STOP. Show the preview to the user and ask them to confirm explicitly in chat (for example: yes, confirm, proceed). Wait for that reply. Only then call the matching create/submit/update tool with values from structuredContent. Do NOT call that tool in the same turn as the preview. Do NOT treat the user's original request as confirmation. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. --- Prepares and previews task creation data in Profit.co. This tool is read-only and does not create data. Use this tool when the user wants to create a task, add a task, or create a to-do. Typical flow: 1) Call this tool first with `subject` (required) and optional `dueDate`, `statusName`, and `priorityName`. 2) The tool returns a confirmation-ready preview (`pending_user_confirmation`) and may show the task preview card. 3) Wait for confirmation: card Confirm when the UI renders; otherwise If the confirmation card/UI is not visible or was skipped: STOP. Show the preview to the user and ask them to confirm explicitly in chat (for example: yes, confirm, proceed). Wait for that reply. Only then call the matching create/submit/update tool with values from structuredContent. Do NOT call that tool in the same turn as the preview. Do NOT treat the user's original request as confirmation. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. 4) After user confirmation, call `create_task` with values from structured content. Parameters: - `subject` (required) - `dueDate` (optional) - `statusName` (optional; defaults to `Not Started` when not provided) - `priorityName` (optional; defaults to `High` when not provided) Assignee behavior: - Task is assigned to the current user by default in this flow. Do not report task creation success until `create_task` succeeds. Do not expose internal identifiers (for example, assigneeEmployeeId) in user-facing text.

Prepares and previews the data required to update a task in Profit.co. Use this tool when the user wants to update a task but has not yet confirmed the changes. It accepts the task identifier and the fields to update, such as subject, description, due date, comment, status, or priority. When sufficient information is available, the tool returns a preview of the task update and may present a confirmation interface. This tool does not create or modify any data. When this returns status `pending_user_confirmation`: if the confirmation card renders, wait for the user to click Confirm before calling the matching create/submit/update tool. Do not ask the user to type yes/confirm/proceed in chat when the card is visible—the card is the only confirmation UI needed. If the confirmation card/UI is not visible or was skipped: STOP. Show the preview to the user and ask them to confirm explicitly in chat (for example: yes, confirm, proceed). Wait for that reply. Only then call the matching create/submit/update tool with values from structuredContent. Do NOT call that tool in the same turn as the preview. Do NOT treat the user's original request as confirmation. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. --- Prepares a task update preview for user confirmation. This tool is read-only and does not update data. Use this tool after the user selects a task from `get_tasks_for_update` and specifies one or more fields to change (subject, description, dueDate, comment, statusName, and/or priorityName). Provide: - `activityId` (required) - only the fields the user wants to update The tool returns a preview and confirmation UI when available. Confirmation (required before `update_task`): - If the confirmation card renders: wait for Confirm on the card. - If the confirmation card/UI is not visible or was skipped: STOP. Show the preview to the user and ask them to confirm explicitly in chat (for example: yes, confirm, proceed). Wait for that reply. Only then call the matching create/submit/update tool with values from structuredContent. Do NOT call that tool in the same turn as the preview. Do NOT treat the user's original request as confirmation. When the user replies confirm, yes, or proceed after a preview: call the matching create/submit/update tool once using parameters from that preview structuredContent. Do NOT call the preview tool again to re-show the preview. CRITICAL — Profit.co identity only: For ownerId, ownerTypeId, ownerName, assigneeEmployeeId, assigneeName, and any employee or owner identifier, use ONLY values returned by Profit.co MCP tools (especially preview structuredContent). NEVER use the MCP host, agent, IDE, or chat client login username, display name, user id, or any identity inferred from Cursor, ChatGPT, or the conversation environment. Do not invent, guess, or substitute owner or assignee names or ids. When calling create/submit/update after preview confirmation, copy owner and assignee fields exactly from that preview structuredContent; do not add, change, or substitute them. If a field is missing from structuredContent, omit it so the server resolves it from the authenticated Profit.co session—never fill it from the client login. The server re-validates employee ids and names against the Profit.co assignable-employee directory; unvalidated values are ignored and the session user is used instead. After user confirmation, call `update_task` using the preview values.

Lists the signed-in user's tasks in Profit.co along with available status and priority options for task updates. Use this tool when the user wants to select an existing task to update and needs the available update options. This tool retrieves the user's current tasks and the valid status and priority values from Profit.co. It does not create or modify any data. --- Lists tasks and update options for the signed-in user in Profit.co. This tool is read-only. Use this tool when the user wants to update an existing task. Behavior: - Returns the user's task list. - Returns the exact available status options and priority options from Profit.co, including custom values. Usage guidance: 1) Call this tool first in the task-update flow. 2) Show the user: - numbered task list, - full status option list (exact values), - full priority option list (exact values). 3) Ask the user to choose a task and fields to update (subject, description, due date, comment, status, or priority). 4) For status and priority updates, use values from the returned option lists. Do not replace returned status or priority options with generic examples.