Breeze

Delete one or more project discussion messages — PERMANENT, this CANNOT be undone. Pass a `message_ids` array (up to 10). ALWAYS two-step, even for a single message: call once to preview, then again with confirm: true. You can only delete your own messages unless you're a team owner/admin. Needs the 'write' scope.

breeze_delete_project_messages

Delete one or more logged time entries — PERMANENT, this CANNOT be undone. Card and project tracked totals are recomputed. Pass an `entry_ids` array (up to 10). ALWAYS two-step, even for a single entry: call once to preview, then again with confirm: true. You can only delete your own entries unless you're a team owner/admin. Needs the 'write' scope and time-tracking permission.

breeze_delete_time_entries

Delete one or more to-dos (checklist items) — PERMANENT, there is no recycle bin and this CANNOT be undone. Pass a `todo_ids` array (up to 10). ALWAYS two-step, even for a single item: call once to preview, then again with confirm: true. Needs the 'write' scope; observers can only delete todos if allowed.

breeze_delete_todos

Return a short-lived download link for a file attached to a task, so you can fetch and read it yourself (e.g. with curl). Pass the attachment_id from breeze_get_card or breeze_search. Link attachments (files stored elsewhere, like Drive or Dropbox) return their own URL unchanged. The link expires in 15 minutes. Read-only: nothing is changed.

breeze_get_download_url

Get full details of a single card (task): description, assignees, start/due dates, status, tags, time tracked, planned time, custom fields, attachments, and comment count.

breeze_get_card

Get the current authenticated Breeze user: identity, team, role, permission flags, and how many projects they can access. Call this first to learn who you are acting as.

breeze_get_me

Get full details of a project the user can access: stages (board columns, ordered), members, available statuses, and time/plan totals.

breeze_get_project

Project overview stats: total cards, done vs open, card counts by stage / status / assignee, due-date buckets (overdue / today / upcoming / none), and time totals (tracked / planned, shown only if you have time-tracking / estimate permission).

breeze_get_project_stats

Record that one task DEPENDS ON one or more other tasks. The card shows these as 'This task depends on', and the dependent tasks show 'Tasks that depend on this task'; the Gantt chart draws them as arrows. Pass card_id (the task that is blocked) and depends_on_ids (the tasks it waits for) — up to 25 per call. All tasks must be in projects you can access, and the card's project must have task dependencies enabled. Linking more than one is two-step: call once to preview, then again with confirm: true. To reference a task inside a comment or description instead of creating a dependency, use the card_refs option on the comment/card tools. Needs the 'write' scope; observers cannot link tasks.

breeze_link_cards

Activity / audit feed (newest first). Pass card_id for a single card's full history, or project_ids (or omit for all accessible projects) for a project-wide feed, optionally filtered by user_ids. Filter the event kind with action_types (the verb: create/update/move/destroy/delete/reactivate — pass ["create"] for CREATION events) and/or actions (the subject: comment/name/todo/member/tag/stage/cardstatus/duedate/startdate/desc/tracked_time/planned_time/card_attach/note/custom_field/...). Returns structured entries — action, action_type, who, which card, when, and stripped text/old_text — for you to narrate. Filter the window with created_after/created_before (e.g. 'what changed this week').

breeze_list_activity

List/count cards (tasks). Pass project_id for one project, or OMIT it to query ALL accessible projects. Natural shortcuts: due (overdue/today/this_week/upcoming/none, timezone-aware) and unassigned — prefer these over computing dates yourself. Other filters: stage_id, assignee_id, status_id, done, tags, swimlane_id, custom_fields, and explicit ranges for due / start / created / updated. stage_id/status_id/assignee_id are numeric ids — resolve names first via breeze_get_project (stages, statuses) or breeze_list_team_members (people). Returns compact card summaries (incl. created_at/updated_at) with a total count. Paginated. (For keyword text matching use breeze_search; for fuzzy/meaning use breeze_semantic_search.)

breeze_list_cards

List/count comments. With card_id: that one card's full thread — archive-aware (works for archived cards) and oldest-first, the natural reading order. Without card_id: a cross-card feed (newest first) over active cards — answers 'comments created today', 'comments by user X', 'comments in project Y today'. Pass project_id to scope the feed to one project, or omit both for all accessible projects. Filters: author_id and date ranges for created / updated. `body` is plain text; pass include_html: true to also get each comment's `body_html`, which you need ONLY when you intend to edit one (it is several times larger, so leave it off for reading). Paginated.

breeze_list_comments

List cards assigned to the current user across all accessible projects ('my tasks'). Filter by done flag and/or due bucket (overdue/today/this_week/upcoming/none) — e.g. due:'overdue' for 'my overdue tasks'. Sorted by due date.

breeze_list_my_cards

List messages in a project's discussion (the project chat room, separate from card comments). Pass project_id. Newest first, paginated. Use the returned message ids with breeze_update_project_message.

breeze_list_project_messages

List projects the current user can access. Optionally filter by workspace. Returns id, name, slug, workspace, color, and card count. Paginated.

breeze_list_projects

List tags (with card counts) for a project, or across all accessible projects if project_id is omitted. Returns id, name, color, project_id, cards_count. Tags are per-project.

breeze_list_tags

List users the current user can see (their team, or co-members of their projects), plus the team's user groups. Use to resolve names to user ids for assignees and for @mentions. A group is mentioned by its `mention_id` — pass that in the `mentions` option of the comment, card or message tools.

breeze_list_team_members

List logged time entries, filtered by project, card, user, and date range. Requires time-tracking permission.

breeze_list_time_entries

List/count to-do (checklist) items as first-class objects, across cards and projects — the way to answer questions like 'todos created this week' or 'todos assigned to X'. Pass project_id for one project, card_id for one card, or OMIT both to query ALL accessible projects. Filters: assignee_id (the todo's own assignee), unassigned, done, todo_list_id, and date ranges for created / updated / due / start. Each todo carries its list name, parent card, assignee_ids and timestamps. Paginated, newest-first. (To read one card's checklist grouped by list, use breeze_get_card instead.)

breeze_list_todos

List the workspaces in the current user's team. Workspaces group projects. Team owners/admins see all workspaces; members see only workspaces containing their projects.

breeze_list_workspaces

Log one or more time entries on a card, in MINUTES. Pass card_id and an `entries` array; each entry takes minutes and optionally logged_date (ISO8601, defaults to today), notbillable, and a desc — so a week of work can be logged in one call. Updates the card's and project's tracked totals automatically. Up to 25 per call. Logging more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope and time-tracking permission.

breeze_log_time

Remove the dependency link between one task and one or more others, in whichever direction it was created. Pass card_id and unlink_ids (up to 10). This only removes the link — no task is deleted. Two-step at ANY count: call once to preview, then again with confirm: true. Needs the 'write' scope; observers cannot change links.

breeze_unlink_cards

Rename a to-do list (checklist group). Pass todo_list_id and the new name. Needs the 'write' scope; observers cannot edit cards.

breeze_update_todo_list

Rename or reorder a stage (list/column). Pass stage_id plus name and/or position (1-based left-to-right). Needs the 'write' scope; only a team owner or admin can change a project's lists.

breeze_update_stage

Bring one or more archived cards back onto the board (undo breeze_delete_cards), along with their list if that was archived too. Pass a `card_ids` array (up to 25). Find archived card ids with breeze_search (only_archived: true). No confirmation needed — restoring only adds things back. Needs the 'write' scope; only a team owner/admin or a project admin with archive rights.

breeze_restore_cards

Bring back one or more deleted projects (undo breeze_delete_project) so they and their cards reappear. Pass a `project_ids` array (up to 25). Only archived items can be brought back — permanently-deleted things (comments, time, estimates, todos, messages) cannot. No confirmation needed — restoring only adds things back. Needs the 'write' scope; only a team owner or admin.

breeze_restore_projects

Bring back one or more archived stages (lists/columns) and the cards that were archived with them (undo breeze_delete_stages). Cards archived separately (not part of a list's deletion) are left alone. Pass a `stage_ids` array (up to 25), and restore_cards: true to bring back EVERY card currently archived in those lists regardless of when. No confirmation needed — restoring only adds things back. Needs the 'write' scope; only a team owner, admin, or project admin.

breeze_restore_stages

EXACT keyword / full-text search (Postgres) across Breeze content: cards, comments, projects, todos, notes, tags, attachments. Matches the literal words you pass in the text — it does NOT understand synonyms, paraphrases, or vague / misspelled / ambiguous names. Use it when you know the actual term. For fuzzy or meaning-based queries, or to resolve a vague project/task name to an id, use breeze_semantic_search instead. Supports the same filters as the Breeze search: project_ids, types, status_ids, assignee_ids, stage_ids, tags, swimlane_ids, custom_fields, updated_after/before, archived.

breeze_search

MEANING-BASED (semantic / RAG) vector search over the AI index, across the user's accessible Breeze content (cards, comments, projects, notes, todos, time entries, estimates). Best for fuzzy, natural-language, paraphrased, or ambiguous queries, and for RESOLVING VAGUE project/task names to ids when you don't know the exact words. For an exact known keyword/term, breeze_search is faster and precise. Returns ranked matches with object_type, object_id, project_id, similarity, and a preview.

breeze_semantic_search

Add one or more estimates to a card, in MINUTES. Pass card_id and an `estimates` array; each takes minutes and optionally logged_date (ISO8601). Updates the card's planned time and the project's total planned. Up to 25 per call. Adding more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope and estimate permission.

breeze_set_estimates

Edit an estimate. Pass estimate_id plus minutes and/or logged_date (ISO8601). Card planned time and project total planned are recomputed. You can only edit your own estimates unless you're a team owner/admin. Needs the 'write' scope and estimate permission.

breeze_update_estimate

Update a project's settings. Pass project_id plus any fields to change: name, description, workspace_id (move it under a workspace; pass null to ungroup), budget_hours, hourly_rate, or start/due dates (ISO8601). Only the fields you pass are changed. Needs the 'write' scope; only a team owner or admin can change project settings.

breeze_update_project

Edit a logged time entry (from breeze_list_time_entries). Pass entry_id plus any of minutes, logged_date (ISO8601), notbillable, desc. Card and project tracked totals are recomputed. You can only edit your own entries unless you're a team owner/admin. Needs the 'write' scope and time-tracking permission.

breeze_update_time_entry

Apply the SAME change to one or more to-dos (checklist items): rename them, mark them done/undone, or set a duedate. Pass a `todo_ids` array (up to 25) and the fields to change — every listed to-do gets the same values, so for different changes call once per distinct change. Updating more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope; observers cannot edit cards.

breeze_update_todos

Add one or more teammates to a project so they can see and work on it. Pass project_id and a `user_ids` array (from breeze_list_team_members). Idempotent. Up to 25 per call. Adding more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope; only a team owner or admin can manage project members.

Create one or more cards (tasks) in a project's stage (list/column). Requires the numeric project_id and stage_id — resolve them first with breeze_get_project (its stages) — plus a `cards` array. Each card takes a name and optionally start/due dates (ISO8601), a description, assignee_ids (from breeze_list_team_members) and tag_ids. Up to 25 cards per call — to create more, call again with the next batch. Creating more than one is two-step: call once to preview, then again with confirm: true. Cards are appended to the bottom of the stage. Needs the 'write' scope; observers cannot create cards.

Post one or more comments on a card. Pass card_id and a `bodies` array (HTML is allowed; plain text is wrapped as-is). @mentions are rendered as text but do NOT send notifications in this version. Up to 25 per call. Posting more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope; observers cannot comment.

Post one or more messages in a project's discussion (the project chat room, separate from card comments). Pass project_id and a `bodies` array. The room is created on first use. @mentions render as text but do NOT notify in this version. Up to 25 per call. Posting more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope; observers cannot post.

Create one or more projects. Pass a `projects` array; each takes a name and optionally a workspace_id (to group it, from breeze_list_workspaces), stage names (the board lists/columns in order — defaults to To-do / Doing / Done), and member_ids to add teammates. The caller is added as owner automatically. Up to 25 per call. Creating more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope; only a team owner or admin can create projects.

Apply the SAME change to one or more cards (tasks). Pass a `card_ids` array (up to 25) plus the fields to change: name, description, start/due dates (ISO8601), done (true/false), assignee_ids, or stage_id to MOVE them to another list/column (resolve stage_id via breeze_get_project). Only the fields you pass are changed, and every listed card gets the same values — for different changes to different cards, call once per distinct change. Updating more than one card is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope; observers cannot edit cards (they may only move them, if allowed).