monday.com

Work management on monday.com. Create and organize boards, move items through stages, assign owners, and post updates.

Measured routing accuracy

64 golden cases replayed through the router over the whole index: measured over corpus ea4f12ad2948 (65 toolkits, 2283 tools indexed and 13 declared uncallable), 32 cases written by hand and 32 cases from the paraphrase pass. A case counts as top-1 when its gold tool ranked first and top-8 when it reached the slate at all.

The sweep is offline: the reranker is a deterministic identity fake that returns candidates in the order retrieval produced them, so top-1 measures retrieval order rather than a reranked slate. just eval-live measures the same cases through the live reranker.

Authentication

Connect an entity with ConnectionsService.InitiateConnection, naming this toolkit's slug. Credentials stay in the connections vault; callers hold connected-account ids only.

oauth2

api_key

Submit the key with ConnectionsService rather than putting it in a request; it is sealed at rest and never returned.

Tools

32 action tools. The catalog-wide slug is monday.<tool>, which is what search_tools returns and call_tool takes.

monday.create_board

Create a new monday.com board to track a project or workflow. Use when the user wants to start, set up, or spin up a new board, sheet, or workspace tracker. Optionally places it in a workspace and sets public, private, or share visibility.

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "spin up a new tracker", "start a fresh project sheet", "set up somewhere to track this work", "make a new place to plan a project", "open a blank sheet for this".

monday.get_board

Get one board's name, description, kind, and workspace by id. Use for a specific known board. To browse many boards, use list_boards or list_workspace_boards.

Class read (reads only). No scopes beyond the connection's defaults. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "what's this board called", "pull up the details for this sheet", "show me info about this tracker", "look up a specific board by id", "get the details for one single board", "check on just this one board".

monday.list_boards

List all boards on the account, newest first. Use when the user wants to browse or see what boards exist, with no single workspace named. Scoped to one workspace instead: list_workspace_boards.

Class read (reads only). No scopes beyond the connection's defaults. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "what trackers do we have", "show me everything I'm tracking", "browse what sheets exist", "see all the boards on this account", "list every board on this account", "give me the full list of boards", "board directory for the whole account".

monday.rename_board

Rename a board. Use when the user wants to retitle, rename, or relabel an existing board. For its groups or items instead, use rename_group or update_item_columns.

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "give this tracker a new name", "retitle this sheet", "call this board something else", "change what this project is labeled", "rename this board to something new", "give the board itself a different name".

monday.archive_board

Archive a board, hiding it from active views. Use when the user wants to archive, retire, or put away a whole board. Items and history are kept; the board can be restored from the archive later.

Class destructive (held by the mutation gate until the call's own arguments carry "confirm": true). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "put this whole tracker away", "retire this sheet, we're done with it", "hide this board from the active list", "shelve this project for now".

monday.duplicate_board

Duplicate a board, structure and optionally its items and updates, as a fresh copy. Use when the user wants to copy, clone, or reuse a board as a template for a new project.

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "copy this tracker as a template", "reuse this board's setup for something new", "clone this sheet's structure", "make a fresh copy of this project layout".

monday.create_group

Add a new group (a section or column of items, like a workflow stage) to a board. Use when the user wants a new group, section, or stage on a board, such as "To Do" or "In Review".

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "add a new stage to this board", "make a section for a new phase", "I need another column of work here", "set up a "to do" section".

monday.list_groups

List the groups (sections or workflow stages) on a board, with each group's id, title, and color. Use to see the stages a board is organized into before filing or moving an item.

Class read (reads only). No scopes beyond the connection's defaults. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "what stages does this board have", "show me the sections on this sheet", "what columns of work exist here", "list every group on this board", "show all the groups on this sheet".

monday.rename_group

Rename a group (section or stage) on a board. Use when the user wants to rename, relabel, or retitle a group, such as changing "To Do" to "Backlog".

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "call this section something else", "retitle this stage", "change this group's label", "rename this workflow phase".

monday.delete_group

Permanently delete a group and every item inside it. Use when the user wants to delete, remove, or get rid of a whole section, not a single item. Irreversible; for one item use delete_item instead.

Class destructive (held by the mutation gate until the call's own arguments carry "confirm": true). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "get rid of this whole section", "wipe out this stage and everything in it", "remove this column of work for good".

monday.create_item

Create a new item (a task, row, or ticket) on a board, optionally inside a group and with initial column values. Use when the user wants to add, file, or create a new task, row, or entry on a monday.com board.

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "add a new task to this board", "file a row for this piece of work", "log a new entry on the sheet", "open a ticket on this tracker", "start tracking this as a task".

monday.get_item

Get one single item's status and full details by id: name, state, board, group, and all column values. Use for one specific known item, not for browsing many items on a board (use list_items).

Class read (reads only). No scopes beyond the connection's defaults. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "what's the status on this task", "pull up the details for this row", "show me everything about this entry", "get one single task's full details", "look up just this one item by id".

monday.list_items

List items on a board, paged, with their name, state, and group. Use when the user wants to see what's on a board or browse its rows and tasks. For one known item, use get_item; to find items by column value, use search_items.

Class read (reads only). No scopes beyond the connection's defaults. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "what's on this board", "show me everything in this tracker", "browse the rows on this sheet", "what tasks exist here", "list every item on this board", "give me the full list of tasks here".

monday.search_items

Find items on a board whose column contains a matching value, such as a status, owner, or text field. Use when the user names a value to search or filter by rather than browsing every row. For a keyword across item names, list and filter with list_items instead.

Class read (reads only). No scopes beyond the connection's defaults. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "find the row where someone put a value", "look for tasks matching a field", "dig up entries with a certain status or owner", "filter this board by a column value", "search for items matching a field value".

monday.update_item_columns

Set several column values on an item at once (status, person, date, text, numbers) from a JSON map keyed by column id. Use for a bulk or multi-field edit. For just the status, owner, or due date, the dedicated set_item_status, assign_item, or set_item_due_date tool is simpler.

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "change a bunch of fields on this task at once", "update several details on this row in one go", "bulk edit this entry's fields", "update multiple columns on one task together".

monday.set_item_status

Set an item's status column to a given label, such as marking a task Done, Working on it, or Stuck. Use when the user wants to change, mark, or update a task's status or progress. Name the status column's id if the board has more than one.

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "mark this task done", "move this to working on it", "flag this row as stuck", "update the progress on this task".

monday.assign_item

Assign a person to an item's owner or assignee column. Use when the user wants to assign, hand off, or put someone's name on a task. Name the person column's id if the board has more than one people column.

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "hand this task to someone", "put someone's name on this row", "make someone the owner of this task", "route this piece of work to a person".

monday.set_item_due_date

Set an item's due date column. Use when the user wants to set, change, or clear a task's deadline or due date. Name the date column's id if the board has more than one date column.

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "when is this task due", "put a deadline on this row", "remind me this is due next week", "clear the deadline on this task".

monday.move_item_to_group

Move an item into a different group on the same board. Use when the user wants to move, shift, or advance a task into another section or workflow stage, such as from "In Progress" to "Done".

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "shift this task into another stage", "advance this row to the next phase", "send this task to a different section".

monday.duplicate_item

Duplicate an item on its board, optionally carrying over its updates. Use when the user wants to copy, clone, or reuse a task as the base for a new one.

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "copy this task as a starting point", "clone this row for a new entry", "reuse this task as a template".

monday.archive_item

Archive a single item, hiding it from active board views. Use when the user wants to archive or put away one task or row. The item can be restored from the archive later; for a whole group use delete_group instead.

Class destructive (held by the mutation gate until the call's own arguments carry "confirm": true). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "put this one task away", "hide this row from the active view", "shelve this single entry".

monday.delete_item

Permanently delete a single item. Use when the user wants to delete or remove one task or row for good. Irreversible; for hiding it instead, use archive_item.

Class destructive (held by the mutation gate until the call's own arguments carry "confirm": true). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "get rid of this task for good", "wipe this row off the board", "remove this single entry permanently".

monday.create_subitem

Create a subitem (a sub-task) under a parent item. Use when the user wants to break a task down, add a checklist item, or add a step under an existing item.

Class write (writes, no confirmation needed). Scopes boards:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "break this task into a smaller step", "add a checklist item under this", "log a sub-task for this row".

monday.list_subitems

List the subitems (sub-tasks) under a parent item. Use when the user wants to see the checklist or breakdown under one item.

Class read (reads only). No scopes beyond the connection's defaults. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "what's the breakdown under this task", "show me the checklist for this row", "see the smaller steps under this entry".

monday.create_update

Post an update (a comment) on an item. Use when the user wants to comment, note, or post a status update on a task, not create a new item or subitem.

Class write (writes, no confirmation needed). Scopes updates:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "leave a note on this task", "post a status note on this row", "comment on this piece of work".

monday.list_updates

List the updates (comments) posted on an item, newest first. Use when the user wants to see the comment history, discussion, or activity notes on a task.

Class read (reads only). No scopes beyond the connection's defaults. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "what's been said about this task", "show the discussion on this row", "see the activity history for this entry".

monday.delete_update

Permanently delete one update (comment) by its own id. Use when the user wants to remove or delete a specific comment or post, not the item it was written on.

Class destructive (held by the mutation gate until the call's own arguments carry "confirm": true). Scopes updates:write. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "take back that note I left", "remove a specific comment for good", "erase one post from this task's history", "delete one single update by its own id".

monday.get_me

Get the identity the connected monday.com account is authenticated as: id, name, and email. Use to check which user or account a connection is running as, not to look up a teammate.

Class read (reads only). Scopes me:read. Calls POST /v2.

Takes no arguments.

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "who am I connected as here", "which account is this hooked up to", "whose login is this integration using", "get my own identity on this connection".

monday.list_users

List every user (person) on the connected monday.com account, with name and email. Use to find a person's user id before assigning them to an item, or to see who has access to the account.

Class read (reads only). Scopes users:read. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "who has access to this account", "find someone's id so I can hand them a task", "show me the people on this account", "list every user on this account", "give me the full directory of people here".

monday.list_teams

List the teams on the connected monday.com account and their members. Use when the user asks who is on a team, or wants to see how people are grouped, rather than the whole account's user list.

Class read (reads only). Scopes teams:read. Calls POST /v2.

Takes no arguments.

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "who's on this team", "how are people grouped here", "show me the squads on this account".

monday.list_workspaces

List the workspaces on the connected monday.com account. Use when the user wants to see what workspaces exist before creating or finding a board inside one.

Class read (reads only). Scopes workspaces:read. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "what workspaces exist on this account", "show me where I could put a new board", "browse the top-level places things live here".

monday.list_workspace_boards

List the boards filed inside one named workspace. Use only when the user points at a particular workspace. Without a workspace named, use list_boards instead.

Class read (reads only). Scopes workspaces:read, boards:read. Calls POST /v2.

Arguments:

Result fields (the payload is trimmed to these before it reaches the model):

Also retrieved by: "what trackers live in this workspace", "show me the sheets inside this workspace", "browse everything filed under this one workspace", "list every board inside this one workspace", "show all boards filed under this workspace".