Get Board Items Page
get_board_items_pageGet paginated items from a monday.com board with optional column values, descriptions, and subitems. Use filters and sorting for targeted data.
Instructions
Get all items from a monday.com board with pagination support and optional column values and item descriptions. Returns structured JSON with item details, creation/update timestamps, and pagination info. Use the nextCursor parameter from the response to get the next page of results when has_more is true. To retrieve an item description (the rich-text body/details of a monday.com item), set includeItemDescription to true — the response will include the item description document blocks with their content, type, and id. Use this whenever the user asks about an item description, body, details, or notes. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board structure (column IDs, column types, status labels, etc.), first use get_board_info to understand the board metadata. This is essential for constructing proper filters and knowing which columns are available. [REQUIRED PRECONDITION]: For board-relation / cross-board linking tasks, call link_board_items_workflow before using this tool. VIEW-BASED FILTERING: If the user refers to a board view by name (e.g. "show me items in the Overdue view"), first call get_board_info to get the board views, find the matching view by name, then extract its filter field and pass it as the filters argument here.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| boardId | Yes | The id of the board to get items from | |
| itemIds | No | The ids of the items to get. The count of items should be less than 100. | |
| searchTerm | No | The search term to use for the search. - Use this when: the user provides a vague, incomplete, or approximate search term (e.g., “marketing campaign”, “John’s task”, “budget-related”), and there isn’t a clear exact compare value for a specific field. - Do not use this when: the user specifies an exact value that maps directly to a column comparison (e.g., name contains "marketing campaign", status = "Done", priority = "High", owner = "Daniel"). In these cases, prefer structured compare filters. | |
| limit | No | The number of items to get | |
| cursor | No | The cursor to get the next page of items, use the nextCursor from the previous response. If the nextCursor was null, it means there are no more items to get | |
| includeColumns | No | Whether to include column values in the response. PERFORMANCE OPTIMIZATION: Only set this to true when you actually need the column data. Excluding columns significantly reduces token usage and improves response latency. If you only need to count items, get item IDs/names, or check if items exist, keep this false. | |
| includeItemDescription | No | Whether to include the item's description in the response. The item description is the rich-text body content that appears inside a monday.com item (similar to a task description or issue body). Set this to true when the user asks about an item's description, details, body, or notes. PERFORMANCE OPTIMIZATION: Only set this to true when you actually need the item description content. | |
| includeSubItems | No | Whether to include sub items in the response. PERFORMANCE OPTIMIZATION: Only set this to true when you actually need the sub items data. | |
| subItemLimit | No | The number of sub items to get per item. This is only used when includeSubItems is true. | |
| filters | No | The configuration of filters to apply on the items. Use get_board_info for column ids and types on the board. Before sending the filters, use get_column_type_info with fetchMode "guidelines" and use data.guidelines.filter (null if that type has no documented rules). | |
| filtersOperator | No | The operator to use for the filters | and |
| columnIds | No | The ids of the item columns and subitem columns to get, can be used to reduce the response size when user asks for specific columns. Works only when includeColumns is true. If not provided, all columns will be returned | |
| orderBy | No | The columns to order by, will control the order of the items in the response |