archive_tasks
ChatGPTImmediately soft-delete up to 20 explicitly identified existing tasks from active work and dispatch subscribed external deletion webhooks. Every task requires its current version. Reuse an idempotency key only for retries of the same arguments. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
create_board
ChatGPTImmediately add one registered board type under an existing authorized project, including template columns and groups. Lead-generation and booking boards also get draft forms and initial settings; this does not publish their forms. Reuse an idempotency key only for retries of the same arguments. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
create_project
ChatGPTImmediately add one project, its canonical task board, and requested memberships within the authorized Taskeya workspace; include it in this connection project boundary. Existing work is not overwritten. Reuse an idempotency key only for retries of the same arguments. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
create_tasks
ChatGPTImmediately create up to 20 tasks in existing authorized boards after autonomous-write consent. Each entry creates one task; this tool cannot update existing tasks. Creation can deliver notifications and trigger configured automations and external webhooks. Reuse an idempotency key only for retries of the same arguments. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
get_action_batch
ChatGPTGet status and redacted execution results for an owned proposal batch. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
get_my_work
ChatGPTList authorized-project tasks assigned to the connection owner. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
get_project
ChatGPTGet one currently authorized project. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
get_project_metrics
ChatGPTGet project metrics and chart datasets for completion trends, stages, and team contribution. Use the returned project name and date range in charts; omit empty charts. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
get_project_report
ChatGPTGet one draft report with block hashes for safe proposals. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
get_task
ChatGPTGet one authorized task and its optimistic-concurrency version. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
get_task_activity
ChatGPTGet redacted, column-filtered activity for one authorized task. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
get_work_changes
ChatGPTList recent task changes inside the authorized-project boundary. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
get_workspace_context
ChatGPTGet the fixed workspace, connection grants, authorized-project count, and pending proposal count. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
list_project_reports
ChatGPTList draft reports in one authorized project. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
list_projects
ChatGPTList only projects inside this connection project boundary. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
list_tasks
ChatGPTList tasks inside authorized projects with visible column values only. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
propose_board_deletion
ChatGPTPrepare deletion of one non-canonical board. Nothing is deleted until the connection owner approves in Taskeya. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
propose_project_deletion
ChatGPTPrepare deletion of one project. Nothing is deleted until the connection owner approves in Taskeya. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
propose_report_draft
ChatGPTSave an approval proposal to create a draft report or update draft report blocks. Supplying replace_batch_id and expected_batch_version replaces the saved proposal and supersedes its previous operations. The report changes only after the owner separately approves in Taskeya; this tool never publishes or shares it. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
propose_task_changes
ChatGPTSave an approval proposal for up to 20 independent task creations, updates, or comments. Supplying replace_batch_id and expected_batch_version replaces the saved proposal and supersedes its previous operations. Tasks and comments change only after the owner separately approves in Taskeya. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
search_tasks
ChatGPTSearch task names inside authorized projects with bounded pagination. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.
update_tasks
ChatGPTImmediately update up to 20 existing authorized tasks after autonomous-write consent. Each entry overwrites supplied fields on one task and requires its current version; this tool cannot create tasks. Updates can deliver notifications and trigger configured automations and external webhooks. Reuse an idempotency key only for retries of the same arguments. In user-facing replies, use project names, task names and links, and people first names. IDs and versions are internal tool arguments: do not display them unless asked. Use a compact table for multiple tasks and returned metrics for charts when useful.