workload.zero

• get_my_profile — Get your own workload.zero profile (name, job title, bio, location, skills).
• update_my_profile — Update your own profile. Pass the fields to change as a JSON object string.
• list_users — List the users of the workspace (id and name). Use the id for direct messages; for task assignment use list_team_members or the user id.
• get_my_colleagues — List the people you share projects with, incl. their team member ids.
• list_team_members — List team members (id | user | type | weekly capacity). The team member id is what projects and task assignments store.
• search — Search across projects, tasks (title, number, linked issue) and users. Example: query "ZERO-41" or "login bug".
• list_notifications — List your notifications, newest first (id | read | title | message).
• mark_notifications_read — Mark one notification as read, or all of them when notificationId is left out.
• get_activity_feed — Recent changes in your projects (who changed what), optionally for one project or one area.
• list_projects — List the projects you have access to (id | code | name | status | client).
• get_project — Get a project: status, client, budget, period, team member ids, task count and description.
• create_project — Create a project. clientId comes from list_clients (or create_client). Example: title "Website relaunch", projectCode "WEB", duration {startDate: "2026-11-01",
• update_project — Update a project. Give only the fields to change, e.g. status "on_hold" or a new end date in duration. The legacy `updates` JSON string is still accepted.
• delete_project — Delete a project you created. It is archived and hidden from all members; tasks and time entries stay in the database.
• get_project_budget — Budget analytics of a project: planned vs. used hours and amount, burn rate.
• list_project_members — List the members of a project (team member id | user id | name | role | weekly hours). Use the team member id for add/update/remove_project_member.
• add_project_member — Add a team member to a project (admin or project manager). teamMemberId comes from list_team_members.
• update_project_member — Change role, weekly hours, capacity or permissions of a project member.
• remove_project_member — Remove a team member from a project. Their tasks stay assigned until you reassign them.
• list_clients — List project clients (id | name | company | email). Use the id as clientId in create_project.
• create_client — Create a project client (admin or project manager).
• list_tasks — List tasks (id | number | title | status | priority | project | assignees | due). Without projectId: your assigned tasks, or with view "all" every task in your
• get_task — Get one task with description, status, priority, assignees, estimate and booked hours, start/due date, tags, linked issue, links, subtask parent, attachments (w
• create_task — Create a task (shown in workload.zero as created by an agent). Example: projectId from list_projects, title "Fix login redirect", priority "high", assignedTo [u
• update_task — Update a task. Give only the fields to change: status, title, description, priority, assignedTo (replaces the list), tags (replaces), deadline, maxHours, linked
• assign_task_to_me — Add yourself to the assignees of a task.
• unassign_me_from_task — Remove yourself from the assignees of a task.
• list_subtasks — List the subtasks of a task. Create a subtask with create_task and parentTaskId.
• move_task_on_board — Move a task to a board column (status) and position (0 = top).
• add_task_link — Add a link to a task, e.g. the pull request, Figma frame or Jira ticket.
• remove_task_link — Remove a link from a task by its position in the links list (0-based, as shown by get_task).
• set_task_work_links — Replace the work result links of a task (what the assignee delivered, e.g. a PR or a deployed preview).
• delete_task — Delete a task (admin, project manager or project lead). It goes to the deleted list and can be restored with restore_task.
• restore_task — Restore a deleted task. Takes the Mongo id from list_deleted_tasks.
• list_deleted_tasks — List deleted tasks of your projects (id | number | title | deleted at).
• get_task_history — Change history of a task: who changed which field from what to what.
• list_task_tags — List the tags used on tasks, optionally for one project.
• add_task_comment — Add a comment to a task, optionally with images (each from an https URL or base64). Images are stored in the project files under tasks/<task number>/.
• update_task_comment — Edit the text of one of your own comments; it is marked as edited. Comments of others can only be deleted (by admins, project managers and project leads), not e
• delete_task_comment — Delete a comment (your own, or any as admin, project manager or project lead).
• toggle_task_comment_reaction — Add your emoji reaction to a comment, or remove it if you already reacted with that emoji.
• attach_file_to_task — Attach an image or file to a task. Give sourceUrl (https) or base64 + fileName, or fileItemId of a file already in workload.zero. The file is stored in the proj
• remove_task_attachment — Remove an attachment from a task and move the file to the trash (your own attachment, or any as admin, project manager or project lead).
• get_my_time_entries — Get your time entries (id | date | hours | project | task | description) with the total.
• list_time_entries — List time entries of everyone you may see (admin and project manager view), filterable by project, user and date.
• log_time — Log time on a project, optionally for a task. Example: projectId, taskId, date "2026-11-04", hours 1.5, description "Code review". With startTime/endTime (HH:mm
• update_time_entry — Change a time entry (hours, date, description, task, start/end time, billable). Give only the fields to change.
• delete_time_entry — Delete one of your time entries. Entries that are already invoiced or approved cannot be deleted.
• start_timer — Start the running timer for a project (and task). Stop it with stop_timer to book the time.
• stop_timer — Stop the running timer and book the time as a time entry.
• get_active_timer — Show the running timer, if any (project, task, start time).
• discard_timer — Discard the running timer without booking any time.
• get_todays_goals — Get your goals for today (id | title | timeframe | task | project | checklist progress).
• get_week_goals — Get your goals for the current week (Monday to Sunday), with checklist progress.
• list_goals — List goals by date range (YYYY-MM-DD) or timeframe, e.g. startDate 2026-11-01, endDate 2026-11-30.
• get_goals_for_task — Get all goals linked to a task (task Mongo id), e.g. to see when work on it is planned.
• create_goal — Create a daily or weekly goal, optionally linked to a task or project, with a checklist; shown in workload.zero as created by an agent. Example: title "Ship inv
• update_goal — Update a goal: date, title, task, project, color, time slot or checklist. Give only the fields to change. The legacy `updates` JSON string is still accepted.
• complete_goal — Mark a goal as completed. Checklist items keep their own state.
• check_goal_item — Tick or untick one checklist item of a goal (index is 0-based, in the order list_goals shows).
• delete_goal — Delete a goal and its checklist. Linked tasks and time entries stay.
• list_my_absences — List your absences (vacation, sick days, comp time) with status.
• list_absences — List the absences you may see as admin or project manager, optionally by date range or status.
• request_absence — Request an absence. Example: type "vacation", startDate "2026-12-22", endDate "2026-12-31". Partial days: startTime/endTime or hours.
• update_absence — Change an absence request (dates, type, reason). Give only the fields to change.
• delete_absence — Withdraw an absence request or delete an absence. The team calendar updates immediately.
• review_absence — Approve or reject an absence request (admin or manager). The employee sees the decision.
• list_invoices — List your invoices (id | number | date | gross total | status | buyer).
• get_invoice — Get an invoice with line items, buyer, totals and status. Accepts the id or the invoice number, e.g. RE-2026-0042.
• create_invoice_from_time — Create a draft invoice from the unbilled time entries of a project in a period.
• create_invoice — Create a draft invoice by hand. It stays a draft: finalizing and sending happen in the app, and finalizing needs a real sender address with a tax number or VAT
• update_invoice — Update a draft invoice. Give only the fields to change; lineItems replaces the whole list; billingEntityId changes the sender and may renumber the draft. Finali
• delete_invoice — Delete a draft invoice. Finalized invoices cannot be deleted.
• record_invoice_payment — Record a (partial) payment on an invoice. Example: amount 1190, paidAt "2026-11-04".
• list_invoice_payments — List the payments recorded on an invoice.
• get_invoice_pdf — Get the PDF of an invoice as an attached file.
• get_revenue — Revenue breakdown of the year (per month, per client).
• get_unbilled_hours — Hours that are tracked but not invoiced yet, per project.
• list_billing_clients — List billing clients (id | company | invoice email | payment terms). Use the id for invoices and quotes.
• list_billing_entities — List your sender entities (id | name | default). Quotes and invoices are issued in the name of one of them.
• create_billing_entity — Create a sender for quotes and invoices. This data is printed on legal documents such as quotes and invoices, so use only what the user gives you and never inve
• update_billing_entity — Update a sender from list_billing_entities. Give only the fields to change. This data is printed on legal documents such as quotes and invoices, so use only wha
• list_quotes — List your quotes (id | number | date | status | customer).
• get_quote — Get a quote with positions, customer, totals and status.
• estimate_quote — Estimate a quote from a scope description. Returns deterministic 'historical' and 'rate-card' variants (each with sum and confidence) plus the context (comparab
• create_quote — Create a quote as a DRAFT. Needs a real sender: billingEntityId from list_billing_entities, or create_billing_entity first with data the user gives you, never i
• update_quote — Update a draft quote. Give only the fields to change; positions replaces the whole list; billingEntityId changes the sender.
• delete_quote — Delete a quote that has not been sent yet. Sent quotes stay for the record.
• get_quote_pdf — Get the PDF of a quote as an attached file.
• convert_quote_to_invoice — Convert an ACCEPTED quote into a draft invoice (positions 1:1).
• send_quote — Send a quote to the client by email. This ONLY works after the user approved the quote for sending in the app. There is intentionally no tool to grant that appr
• list_deals — List deals (id | title | stage | status | value | ref), optionally by stage, pipeline or company.
• get_deal — Get a deal with contacts, company, products, notes and its activities.
• create_deal — Create a deal. Example: title "Website relaunch Acme", value 24000, stage "proposal", companyId, contactIds.
• upsert_deal — Create or update a deal idempotently by campaign ref (derived from the lead email).
• update_deal — Update a deal by id: stage, status, notes, value, loss reason, tags, title, probability, expected close date, contacts, company.
• move_deal_stage — Move a deal to another pipeline stage, e.g. "negotiation".
• mark_deal_won — Mark a deal as won; status won, stage closed_won, counts in reports.
• mark_deal_lost — Mark a deal as lost with a reason, e.g. "Budget moved to 2027".
• link_deal_to_project — Link a won deal to the workload.zero project that delivers it.

No hidden text found in the tool definitions.

Text a person reading a tool definition does not see and a model does. Invisible characters can be pasted in by accident; this says what is there, not why. Covers tools only, not prompts or resources.