Monday MCP

Browse the account-wide catalog of available trigger types and skills for monday platform agents. READ-ONLY — no agent_id required. Use this tool to discover what's available BEFORE wiring anything to a specific agent. ACTIONS: - list_triggers: { block_reference_ids? } — returns available trigger types. Each entry has block_reference_id (required for manage_agent_triggers action:"add"), name, description, field_schemas (describes field_values shape), and required_fields (fields to collect from the user). Note: only triggers that can be added programmatically appear here. OAuth/3rd-party triggers (Slack, Gmail, Salesforce, etc.) require user setup in the monday.com UI and will not appear here. - list_skills: {} — returns available skills with id, name, description. Never guess or invent a skill id — always look it up here before calling manage_agent_skills action:"add". USAGE EXAMPLES: - List all trigger types: { "action": "list_triggers" } - Fetch specific trigger: { "action": "list_triggers", "block_reference_ids": ["some-block-ref-id"] } - List all skills: { "action": "list_skills" } RELATED TOOLS: - manage_agent_jobs — use block_reference_id from list_triggers to configure jobs with nested triggers - manage_agent_triggers — use block_reference_id from list_triggers to attach a trigger to a specific agent - manage_agent_skills — use skill id from list_skills, or action:"create" to author a new skill, then attach to an agent - manage_agent — manage the agent entity itself (create, update, delete, activate, etc.)

Execute read-only GraphQL queries against the monday.com API. Only queries are accepted — mutations are rejected with an error before the request is sent. Use the get_type_details tool first to understand the schema before crafting your query.

Execute GraphQL mutations against the monday.com API to create, update, or delete data. Only mutations are accepted — queries are rejected with an error before the request is sent. Use get_graphql_schema and get_type_details tools first to understand the schema before crafting your mutation.

Execute any monday.com API operation by generating GraphQL queries and mutations dynamically. Make sure you ask only for the fields you need and nothing more. When providing the query/mutation - use get_graphql_schema and get_type_details tools first to understand the schema before crafting your query.

Fetch complete JSON Schema 7 definitions for all available widget types in monday.com. This tool is essential before creating widgets as it provides: - Complete schema definitions for all supported widgets - Required and optional fields for each widget type - Data type specifications and validation rules - Detailed descriptions of widget capabilities Use this tool when you need to: - Understand widget configuration requirements before creating widgets - Validate widget settings against official schemas - Plan widget implementations with proper data structures The response includes JSON Schema 7 definitions that describe exactly what settings each widget type accepts.

This tool allows you to calculate insights about board's data by filtering, grouping and aggregating columns. For example, you can get the total number of items in a board, the number of items in each status, the number of items in each column, etc. Use this tool when you need to get a summary of the board's data, for example, you want to know the total number of items in a board, the number of items in each status, the number of items in each column, etc.[REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info with filters.columns.only to get column metadata without fetching views. This is essential for constructing proper filters and knowing which columns are available.[IMPORTANT]: For some columns, human-friendly label is returned inside 'LABEL_<column_id' field. E.g. for column with id 'status_123' the label is returned inside 'LABEL_status_123' field.

Change the column values of a single item on a monday.com board. [IMPORTANT] If you need to update multiple items in one call, use update_items instead of calling this tool in a loop. Otherwise: change the column values of a single item in a monday.com board. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info with filters.columns.only to get column metadata without fetching views. This is essential for constructing valid column values. For board-relation linking tasks, call link_board_items_workflow before using this tool.

Connect a custom external agent (an agent running on your own server/infra) to monday.com. { custom: { name, callback_url? } } Returns the new agent_id plus a one-time signing_secret and api_token used to verify webhook requests and call the monday.com API/MCP server — both are shown ONLY in this response, so capture them immediately. RULES: - Omitting callback_url creates the agent without a webhook — it won't be mentionable/assignable until one is added. - This tool is for CUSTOM agents only. For Claude, OpenAI, and other supported providers, use manage_agent.

Save a reusable action (a stored code script). Variables are injected as environment variables (access via os.environ in Python, process.env in JS/TS). Recommended: Test your code with execute_code before saving to ensure it works correctly. Network access is restricted to the following hosts: [api.monday.com/, mcp.monday.com/mcp]. Requests to any other host will be blocked. Example: name: "Get board items", description: "Fetches items from a board", language: "python", code: "import requests\nprint('done')"

Creates an automation on a monday board from a structured natural-language description. Use this tool only when you know: - boardId - the user's intended trigger - at least one intended action - any details the user provided that are relevant to the trigger, conditions, or actions The caller does not need to know the exact available automation blocks or their required fields. Describe the user's intent clearly — the tool will translate that intent into supported blocks and values. If a required detail is missing from the user's request, ask for clarification before calling the tool. If the tool returns status: "needs_clarification", present the unresolved fields to the user, gather answers, then call the tool again. Describe the automation in this format: Trigger: When <the event that should start the automation> Details: <relevant detail>: <value> Conditions: - Only if <condition that should be true> Details: <relevant detail>: <value> Actions: - <action the automation should perform>: <relevant detail>: <value> Rules: - Use one trigger. - Conditions are optional. - Multiple conditions mean AND. - Use one or more actions. - Do not use branching. - Use natural language, not block IDs or internal field names. - Actions may reference values from the trigger context, such as "{{item name}}", "{{creator}}", "{{status}}", "{{group}}", or "{{board}}". Terminology: - Trigger: the event that starts the automation, such as "when a new item is created". - Conditions: optional requirements that must be true before actions run. - Actions: what the automation does when it runs. Example: Trigger: When a new item is created Actions: - Send a notification: Recipient: John Snow Title: Important Update Message: The item "{{item name}}" was created. - Move the item to a group: Group: Top group

Create a monday.com board. Use creationPrompt to describe how you want the board to be built

Create a new column in a monday.com board. [REQUIRED PRECONDITION]: If the column needs type-specific configuration (columnSettings) — e.g. status/dropdown labels, formula definitions, number units — first call get_column_type_info with fetchMode "schema" for that column type to learn the valid settings structure. Do not guess the settings shape. To give the new column AI behavior, create it here first, then call configure_ai_column.

Use this tool to create a new monday.com dashboard that aggregates data from one or more boards. Dashboards provide visual representations of board data through widgets and charts. Use this tool when users want to: - Create a dashboard to visualize board data - Aggregate information from multiple boards - Set up a data visualization container for widgets

Create a new monday.com doc either inside a workspace or attached to an item (via a doc column). After creation, the provided markdown will be appended to the document. LOCATION TYPES: - workspace: Creates a document in a workspace (requires workspace_id, optional doc_kind, optional folder_id, optional docOwnerIds) - item: Creates a document attached to an item (requires item_id, optional column_id, optional docOwnerIds) USAGE EXAMPLES: - Workspace doc: { location: "workspace", workspace_id: 123, doc_name: "My Doc", doc_kind: "private" , markdown: "..." } - Workspace doc in folder: { location: "workspace", workspace_id: 123, doc_name: "My Doc", folder_id: 17264196 , markdown: "..." } - Item doc: { location: "item", item_id: 456, doc_name: "My Doc", column_id: "doc_col_1" , markdown: "..." } - Workspace doc with agent owner: { location: "workspace", workspace_id: 123, doc_name: "My Doc", markdown: "...", docOwnerIds: ["<agent_owner_user_id>"] }

Create a new folder in a monday.com workspace

Create a monday.com form. Also creates a backing board to store responses. Returns the formToken for future mutations.

Submit a response to a monday.com WorkForm. Use get_form first to retrieve the WorkForm, then: - Inspect each question's showIfRules to determine which questions are conditionally shown based on previous answers. - Inspect each question's settings for any answer constraints (e.g. rating limits, select options, label limits). - Take note of any titles, descriptions, and content blocks to present the form naturally as you walk the user through it. - Take note of pages and question order to present questions in the correct sequence. Gather all answers upfront before calling this tool — do not submit one question at a time. Accepts a bare form token, a full WorkForm URL (e.g. https://forms.monday.com/forms/{form_token}?r=use1), or a shortened wkf.ms URL (e.g. https://wkf.ms/4tqP28t) — shortened URLs are automatically resolved by following the redirect. Returns the submission ID.

Create a new group in a monday.com board. Groups are sections that organize related items. Use when users want to add structure, categorize items, or create workflow phases. Groups can be positioned relative to existing groups and assigned predefined colors. Items will always be created in the top group and so the top group should be the most relevant one for new item creation

Create a single item or subitem on a monday.com board, or duplicate an existing item. [IMPORTANT] If you need to create multiple items in one call, use create_items instead of calling this tool in a loop. Otherwise: create a new item with provided values, create a subitem under a parent item, or duplicate an existing item and update it with new values. Use parentItemId when creating a subitem under an existing item. Use duplicateFromItemId when copying an existing item with modifications. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info with filters.columns.only to get column metadata without fetching views. This is essential for constructing proper column values and knowing which columns are available.

Create up to 20 new items in a single call. Each item is fully independent - it chooses its own groupId, parentItemId (for subitems), duplicateFromItemId (for bulk templating from an existing item), and createLabelsIfMissing. A single call can therefore span multiple groups, mix regular items with subitems under different parents, and mix fresh creates with duplicates of existing items. Each item returns its own item_id and item_url on success, or a raw error message on failure. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info with filters.columns.only to get column metadata without fetching views. This is essential for constructing proper column values and knowing which columns are available.

Send a notification to a user via the bell icon and optionally by email. Use target_type "Post" for updates/replies or "Project" for items/boards.

Create a new update (comment/post) on a monday.com item. Updates can be used to add comments, notes, or discussions to items. You can optionally mention users, teams, or boards in the update. You can also reply to an existing update by using the parentId parameter.

Create a new board view (tab) with optional filters and sorting. Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text View types: TABLE (standard board), DASHBOARD, FORM, APP

Create a new table-type board view with optional filters, sort, tags, and table-specific settings including conditional coloring (highlight rows/cells based on column values). CONDITIONAL COLORING: Use settings.conditional_coloring to highlight rows or cells. Each rule specifies a column_id, operator, value (human-readable — e.g. "Stuck", not an index), color, and entire_row flag. Example: highlight rows where Status is "Stuck" in red, or where Salary > 100000 in green. Use this tool instead of create_view when you need table-specific settings like column visibility, group-by, or conditional coloring. Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

Create a new widget in a dashboard or board view with specific configuration settings. This tool creates data visualization widgets that display information from monday.com boards: **Parent Containers:** - **DASHBOARD**: Place widget in a dashboard (most common use case) - **BOARD_VIEW**: Place widget in a specific board view **Critical Requirements:** 1. **Schema Compliance**: Widget settings MUST conform to the JSON schema for the specific widget type 2. **Use all_widgets_schema first**: Always fetch widget schemas before creating widgets 3. **Validate settings**: Ensure all required fields are provided and data types match **Workflow:** 1. Use 'all_widgets_schema' to get schema definitions 2. Prepare widget settings according to the schema 3. Use this tool to create the widget

Creates a new empty workflow in the given workspace and returns its identifiers (workflowObjectId and workflowDraftId). Use this tool when the user wants to start a brand-new workflow from scratch, rather than modifying an existing one. Only the workspace is required; title, privacy kind, description, folder, and owners are optional and fall back to sensible defaults. The tool returns a JSON object with the identifiers of the newly created workflow, which can then be used with the other workflow tools. To build a URL to the workflow, use the template: https://<account_slug>.monday.com/custom_objects/<workflowObjectId>. To get a real URL example of the account, call the monday GraphQL MCP tool with the query `{ me { url } }`.

Create a new workspace in monday.com

Delete a saved action. Example: id: "550e8400-e29b-41d4-a716-446655440000"

Delete a board view (tab) from a monday.com board. Use get_board_info to find the view ID before deleting.

Run arbitrary code in a monday-authenticated sandbox, without saving. Prefer dedicated monday tools for individual reads, writes, and GraphQL queries/mutations — they render in the UI and are retried one step at a time. Reach for execute_code when code is genuinely the better tool: - Bulk / multi-item work — batch operations, dedup, aggregations, joins across boards (one script beats N tool calls that accumulate context and compound failure) - Data transformation — normalizing phones/dates, fuzzy matching, weighted scoring - File I/O — parsing uploaded CSV/XLSX to import items, producing downloadable exports - Multi-step workflows where each step's output gates the next The sandbox has authenticated access to the monday.com API. You can make HTTP requests with GraphQL queries and mutations — authentication is handled automatically. IMPORTANT: Network access is restricted to the following hosts: [api.monday.com/, mcp.monday.com/mcp]. Requests to any other host (or a different path on a restricted host) will be blocked. Use this tool to query boards, items, columns, users, updates, and any other monday.com API resource. THE SANDBOX IS PER-CALL: a new empty container every call, destroyed when the call returns. Nothing written to disk survives, /tmp included. Never write a file in one call to read it in a later one, and don't invent staging paths for earlier tool results — none exist. To carry data forward, print it and pass it into the next call's code, or do the whole job in one call. Splitting a fan-out across calls only works if the later calls don't depend on the earlier ones' files. FAIL WITH A NON-ZERO EXIT. A run that prints an error and exits 0 is recorded as a success. The monday.com API returns HTTP 200 with an "errors" array, so check the parsed body rather than the status code and raise when it is present. Let exceptions propagate; don't wrap the script in a bare try/except. TIME LIMIT: 300s. A run that exceeds it is killed, so scope each call to finish well inside the limit instead of fetching everything in one script. Don't call mcp.monday.com from inside the sandbox to reach monday tools — you already have them, and a tool missing from your tool list won't be found there either. Example — monday.com GraphQL query, raising on errors (Python). Use this shape for every API call: code: "import requests\ndef gql(query):\n body = requests.post('https://api.monday.com/v2', json={'query': query}).json()\n if 'errors' in body:\n raise RuntimeError(body['errors'])\n return body['data']\nprint(gql('{ users(limit:5) { id name email } }'))" Example — monday.com GraphQL mutation (Python): code: "import requests\nmutation = 'mutation { create_board(board_name: \"New Board\", board_kind: public) { id } }'\nbody = requests.post('https://api.monday.com/v2', json={'query': mutation}).json()\nif 'errors' in body:\n raise RuntimeError(body['errors'])\nprint(body['data'])" Example — with vars (accessed via os.environ): code: "import os, requests\nuser_id = os.environ['user_id']\nresp = requests.post('https://api.monday.com/v2', json={'query': f'{{ users(ids: [{user_id}]) {{ id name email }} }}'})\nprint(resp.json())" vars: {"user_id": 12345} Example — simple (Python): code: "print('hello world')" Example — with files (input and output): code: "import json\ndata = json.load(open('/tmp/data.json'))\njson.dump({'count': len(data)}, open('/tmp/result.json', 'w'))" files: [{"path": "/tmp/data.json", "content": "W3siaWQiOiAxfV0="}] output_files: ["/tmp/result.json"] Example — auto-collect outputs (write anything you want returned under /outputs): code: "import os, json\nos.makedirs('/outputs', exist_ok=True)\njson.dump({'ok': True}, open('/outputs/result.json', 'w'))" return_outputs: true

Discover meetings by topic, or list/browse meetings by date and access. Returns meetings ranked by keyword relevance (matched against title and AI gist — not semantic). USE THIS FIRST for topic/theme questions ("what did we decide about pricing", "find meetings about the acme deal") AND for listing/browsing ("list my recent meetings", "meetings from last week", "my last 10 meetings"). When query is omitted, returns recent meetings filtered by date/access only — this is the tool for listing. Pass returned ids to get_meetings_content for full content, or to search_meetings_content for matching passages. Only indexed meetings are candidates.

Finalize a file upload and create the asset on monday.com. Call this after uploading the file to the presigned URL from get_asset_upload_url. Requires the etag value from the PUT response headers. Automatically attaches the uploaded asset to the specified file column on the item. Returns the created asset_id.

Create, update, or delete a question in a monday.com form. [REQUIRED PRECONDITION]: For update and delete, call get_form first to resolve the exact question id and see its current type and settings — never guess a question id. For create, get_form shows the existing questions so you do not duplicate one.

Retrieve a saved action by ID. Example: id: "550e8400-e29b-41d4-a716-446655440000"

Get assets (files) by their IDs. Returns file metadata including name, extension, size, public URL (valid for 1 hour), thumbnail URL, upload date, and who uploaded it.

Get a presigned URL to upload a file to monday.com. Returns an upload_id and upload_url. Only call this tool if you can execute a direct HTTP PUT with binary file data and read response headers (e.g. via shell/curl). If you can't, tell the user direct file upload isn't supported here — don't call this tool. After calling this tool, upload the file to the returned URL using an HTTP PUT request and capture the ETag header from the response: curl -i -X PUT "<upload_url>" \ -H "Content-Type: <the contentType you provided>" \ --data-binary @<local_file_path> The response includes an ETag header (e.g. ETag: "abc123...") — save this value. Then call finalize_asset_upload with the upload_id, etag, board_id, item_id, and column_id to complete the upload and attach the file to an item's file column. Max file size: 500MB.

Read automation/workflow run history. Read-only. Modes: - "history": paginated run feed (state, duration, error reason). Use "filters" to narrow results and "nextPageOffset" to page (offset-only — next page = previous offset + returned count). - "detail": single run by "triggerUuid" (required) — returns block steps and MCP tool calls. Set "includeToolEvents": false to skip tool calls. Scope: provide "boardId" for a specific board or "accountWide": true. One is required. Known event states: "success", "failure", "exhausted".

Aggregate automation run statistics. Read-only. Breakdowns: - "totals": success/failure/total counts at the account or board level. - "by_entity": per-automation and per-workflow counts for a given "runStatus" (required: "success" | "failure" | "exhausted"). Use "excludeAutomationIds" to omit specific automations. Scope: provide "boardId" for a specific board or "accountWide": true. One is required. Optional "userIds" narrows results to specific creators.

Get board activity logs for a specified time range (defaults to last 30 days). Optionally filter by item ids or user ids to avoid fetching activity for the entire board. [REQUIRED PRECONDITION]: Call this with includeData=true before undo_action — it is the source of the action_record_uuid that identifies the action to undo.

Get comprehensive board information including metadata, structure, owners, and configuration. Also returns the board's views (e.g. table views, filter views) — each view includes its id, name, type, and a structured filter object. On large boards, ALWAYS narrow the response: use filters.views.names or filters.views.ids when you only need specific views, and/or filters.columns.ids when you only need specific columns. Set filters.views.only or filters.columns.only when you want just that section — full views[].settings across many views can be multi-MB. The response includes hierarchy_type which indicates if the board is a multi-level board ("multi_level") where items can have nested subitems up to 5 levels deep on the same board. On multi-level boards, subitems share the same columns as parent items and subItemColumns will be null. Call this FIRST whenever you are not already familiar with a board structure (column IDs, column types, column revisions, status labels) — before reading or writing its data, or before any tool that declares this as a required precondition (e.g. get_board_items_page, board_insights, create_item, create_items, update_items, change_item_column_values, update_column, create_view, create_view_table, update_view, update_view_table). Also use the views it returns to resolve a view referenced by name (pass that name in filters.views.names), and as the source of view ids for update_view and update_view_table. Each column's "settings" field is the raw API value for that existing column, shown so you can read current labels/config — it is NOT the format expected by the columnSettings parameter of create_column or update_column. Never copy a column's "settings" object verbatim into columnSettings — use get_column_type_info with fetchMode "schema" to get the correct shape for the column type you are creating or updating.

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. [MULTI-LEVEL BOARDS]: The response includes hierarchy_type on the board ("multi_level" for MLS boards) and parent_item_id on each item. On multi-level boards, items form a tree (up to 5 levels). Use includeSubItems to get all descendants (returned flat with parent_item_id to reconstruct the tree). Top-level items have no parent_item_id. Subitems reference their parent. [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 with filters.columns.only to get column metadata without fetching views. This is essential for constructing proper filters and knowing which columns are available. [VIRTUAL COLUMNS]: Four filterable columns exist that get_board_info never returns - "group" (the item's board group), "__creation_log__" (creation time), "__last_updated__" (update time) and "__item_id__" (item id). All four are also valid in orderBy, e.g. "__creation_log__" with direction "desc" to sort newest-first. Call get_column_type_info with the matching column type for each one's compareValue and operator rules. [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 with filters.views.names set to that view name (avoids downloading all views on large boards), extract the matching view's filter field, then pass it as the filters argument here.

Retrieves comprehensive information about a specific column type. Use fetchMode "schema" (default) to get the JSON schema definition from the API — to understand structure, validation rules, and available properties for column settings. Call this BEFORE any tool that writes column settings: create_column, update_column, and manage_object_schema_columns. Use fetchMode "guidelines" to get only guidelines.filter and guidelines.aggregation (no schema, no GraphQL round-trip). Call this before building any filter rule that uses compare_value/operator for that column type — e.g. get_board_items_page, board_insights, or a view's filters (create_view, create_view_table, update_view, update_view_table) — and before building board insights aggregation counts.

Get a monday.com form by its form token, including its pages, questions, question ids, settings, and conditional showIfRules. Form tokens can be extracted from the form's url. Given a form url, such as https://forms.monday.com/forms/abc123def456ghi789?r=use1, the formToken is the alphanumeric string that appears right after /forms/ and before the ?. In the example, the formToken is abc123def456ghi789. Call this FIRST before any tool that acts on an existing form: create_form_submission (to know the questions and their constraints), form_questions_editor (to resolve question ids and current structure), and update_form (to see the current settings before changing them).

Fetch the monday.com GraphQL schema structure including query and mutation definitions. This tool returns available query fields, mutation fields, and a list of GraphQL types in the schema. You can filter results by operation type (read/write) to focus on either queries or mutations.

Fetch full content (summary, topics, action items, transcript) for meetings you already have ids for. Get those ids from explore_meetings (topic/listing/browse) or search_meetings_content (passages) first — this tool is NOT for discovery or listing. Pass the ids with the include_ flags for the content you need (defaults to the summary if none are set). Requested ids that are not returned are listed in `missing_ids` (not found, not accessible, or no completed recording); meetings whose content was dropped to keep the response within its size limit are listed in `content_omitted_ids`. The search param is a narrow case-insensitive substring fallback on title, participant name, or email — NOT topic/keyword search.

Discover monday-dev sprints boards and their associated tasks boards in your account. ## Purpose: Identifies and returns monday-dev sprints board IDs and tasks board IDs that you need to use with other monday-dev tools. This tool scans your recently used boards (up to 100) to find valid monday-dev sprint management boards. ## What it Returns: - Pairs of sprints boards and their corresponding tasks boards - Board IDs, names, and workspace information for each pair - The bidirectional relationship between each sprints board and its tasks board ## Note: Searches recently used boards (up to 100). If none found, ask user to provide board IDs manually.

Ask a question about monday.com and get an AI-generated answer from the official knowledge base. Use kind="general" for questions about using monday.com — features, automations, UI, help center, and settings. Returns cited source articles with links. Use kind="developer_docs" for questions about the monday.com API — GraphQL queries and mutations, authentication, rate limits, webhooks, schema, API best practices, and building apps. Important: do not include PII data in the questions.

Lists the concrete entities (items, boards, docs, ...) the workflow's trigger can be fired on, so the workflow can be run once on one of them. Use this tool: - ALWAYS before calling run_workflow_once, to learn whether the trigger needs an entity and which entities are available. - When the user asks what the workflow would be run on. Do NOT use this tool for a board automation, such as one create_automation built: run-once applies to workflows only, and the id create_automation returns is not a workflowObjectId. Tell the user to trigger that automation on the board instead. The tool does NOT modify the workflow and does NOT run anything. The response is a JSON object: - status "ok": "requiresEntity" tells you whether run_workflow_once needs a triggerPayload, and "entities" is a list of { label, value } candidates. Show the labels to the user and let them pick; pass the picked entity's "value" object verbatim as run_workflow_once's triggerPayload. An empty "entities" list while requiresEntity is true means there is nothing to run on — tell the user instead of guessing a payload. - status "failed": "message" explains why the entities could not be listed. Relay it; do not call run_workflow_once.

List the sprints of a monday-dev sprints board with their metadata. Returns comprehensive sprint metadata including: ## Data Retrieved: A table of sprints with the following information: - Sprint ID - Sprint Name - Sprint timeline (planned from/to dates) - Sprint completion status (completed/in-progress/planned) - Sprint start date (actual) - Sprint end date (actual) - Sprint activation status - Sprint summary document object ID ## Parameters: - **limit**: Number of sprints to retrieve (default: 25, max: 100) Requires the Main Sprints board ID of the monday-dev containing your sprints. If you do not already have it, call get_monday_dev_sprints_boards first to discover it. ## Call this before: - get_sprint_summary — this tool returns the Sprint IDs that get_sprint_summary requires. Never guess a sprint ID.

Get the complete summary and analysis of a sprint. ## Purpose: Unlock deep insights into completed sprint performance. The sprint summary content including: - **Scope Management**: Analysis of planned vs. unplanned tasks, scope creep - **Velocity & Performance**: Individual velocity, task completion rates, workload distribution per team member - **Task Distribution**: Breakdown of completed tasks by type (Feature, Bug, Tech Debt, Infrastructure, etc.) - **AI Recommendations**: Action items, process improvements, retrospective focus areas ## Requirements: - Sprint must be completed and must be created after 1/1/2025 - Requires a sprintId. [REQUIRED PRECONDITION]: call get_sprints_metadata first to list the sprints on the board and resolve the sprintId (and to confirm the sprint is completed). If you do not know the sprints board ID either, start with get_monday_dev_sprints_boards. ## Important Note: When viewing the section "Completed by Assignee", you'll see user IDs in the format "@user-12345678". the 8 digits after the @is the user ID. To retrieve the actual owner names, use the list_users_and_teams tool with the user ID and set includeTeams=false for optimal performance.

Get detailed information about a specific GraphQL type from the monday.com API schema, including its fields, input fields, and enum values. Call this with a known type name to confirm its exact fields, arguments, and enum values before referencing that type in an operation for all_monday_api, all_api_read, or all_api_write, so the fields and arguments you send actually exist.

Get updates (comments/posts) from a monday.com item or board. Specify objectId and objectType (Item or Board) to retrieve updates. For Board queries, you can filter by date range using fromDate and toDate (both required together, ISO8601 format). By default, Board queries return only board discussion. Set includeItemUpdates to true to also include updates on individual items. Returns update text, creator info, timestamps, and optionally replies and assets.

Fetch current user information, account information, and their relevant items (boards, docs, folders, workspaces, dashboards). Use this tool to: - Get context about who the current user is (id, name, title) - Get account info: plan tier, active member count, trial status, and active products - Get the number of active members in the account (returns active_members_count) - Discover user's favorite boards, folders, workspaces, and dashboards - Get user's most relevant boards based on visit frequency and recency - Get user's most relevant docs based on load frequency and recency - Get user's most relevant people based on interaction frequency and recency - Reduce the need for search requests by knowing user's commonly accessed items

Reports how a run started by run_workflow_once ended: whether it succeeded, and if not, which step failed and why. Call this after run_workflow_once, passing the "automationId" it returned. The tool does NOT modify the workflow and does NOT run anything. It answers immediately with whatever is known so far, so a run in progress is a normal answer, not a problem: - "isTerminal": false — the run has NOT finished. This is NOT a failure. Wait "retryAfterMs" milliseconds and call this tool again with the same arguments. Keep doing that until isTerminal is true. Never report an outcome to the user while isTerminal is false; say the run is still going. - "isTerminal": true — the run is over and "state" is its final outcome. Report it and stop calling. Trust "isTerminal" over your own reading of "state". "state" is one of: - "success" — every step ran without error. - "failure" — a step failed. "errorReason" and the failing entry in "blocks" say which and why. - "exhausted" — the run gave up after retrying a step too many times. - "stopped" — the run was stopped before finishing, so the remaining steps never ran. - "zero_actions" — the trigger fired but the workflow's conditions matched nothing, so no step ran. Nothing is broken; the entity did not qualify. - "running" — a step is executing right now. - "waiting" — the run is parked on a wait step or waiting for a second event. This can last hours, which is why "retryAfterMs" is long here. Tell the user it is waiting rather than polling silently for hours. - "not_indexed_yet" — the run's record has not appeared yet, which is expected for the first few seconds after a run starts. It does NOT mean nothing ran. "blocks" lists the steps recorded so far, each with its own "state" and, when it failed, "errorReason". While isTerminal is false this list is partial and is progress, not a verdict. Use it to tell the user which step failed rather than only that the run failed. The response is a JSON object: - status "ok": the fields above. - status "failed": the status could not be read. "message" explains why. This says nothing about the run itself — do not report the run as failed because of it.

A reasoning-focused process planner with deep knowledge of monday.com workflow architecture. Given a description of a process, it returns a structured textual plan describing one or more related workflows that implement it. Use this tool for: - Planning a new workflow or multi-workflow architecture from a process description. - Deciding whether a process should be implemented as a single workflow or multiple related workflows. - Producing a concrete, block-level plan (trigger, steps, route keys) that another agent or human can build from. - Don't tell it about one time actions, like non-repeating resource creations that are needed to set up the process. This tool does NOT have access to any specific workflow's current state — it plans from scratch using all available blocks. It does not execute any changes.

Workflow expert for a single workflow. Given a prompt, answers questions about the workflow's structure and configuration, or makes changes to it (create, update, delete steps, and configure step fields). Delegate any prompt that asks about a workflow or asks to change it. Pass clear, descriptive instructions — the expert will decide the right response or operations. Field values reference resources (boards, columns, people, channels, projects, ...) from monday or any external app — all handled the same way. Pass each resource through as the user stated it; the expert resolves names to IDs and asks the user when it's ambiguous. Pro-tip: pass along any ID you already have to save a follow-up question — no need to look one up first. Constraints: works on ONE workflow at a time.

List all saved actions for the current user.

List all automations on a specific monday.com board, including their ids, titles, active state, and configuration. Returns two groups: "workflows" (fully manageable, supports pagination via limit/cursor) and "legacyAutomations" (READ-ONLY automations set up in an older way — returned on the first page only, when no cursor is given). Always present BOTH groups to the user together as one list of board automations — never omit or hide "legacyAutomations". The split and the read-only limitation are internal context for you only: don't volunteer them and don't label any automation "legacy" or "read-only". Only if the user asks to act on a legacy one, briefly explain it can't be changed (e.g. "This one was set up in an older way and can't be modified here"). Call this FIRST before manage_automations — it is the only way to resolve an automation id from a name or description. Never guess an automation id. When NOT to use: Do not call this tool to get general board information unrelated to automations.

Tool to fetch users and/or teams data. MANDATORY BEST PRACTICES: 1. ALWAYS use specific IDs or names when available 2. If no ids available, use name search if possible (USERS ONLY) 3. Use 'getMe: true' to get current user information 4. AVOID broad queries (no parameters) - use only as last resort REQUIRED PARAMETER PRIORITY (use in this order): 1. getMe - STANDALONE 2. userIds 3. name - STANDALONE (USERS ONLY, NOT for teams) 4. teamIds + teamsOnly 5. No parameters - LAST RESORT CRITICAL USAGE RULES: • userIds + teamIds requires explicit includeTeams: true flag • includeTeams: true fetches both users and teams, do not use this to fetch a specific user's teams rather fetch that user by id and you will get their team memberships. • name parameter is for USER search ONLY - it cannot be used to search for teams. Use teamIds to fetch specific teams.

List all workspaces available to the user, ordered by membership (user's workspaces first). Returns workspaces with their ID, name, and description. [IMPORTANT] To search for workspaces by name, use the "search" tool with searchType WORKSPACES instead — it provides faster and more accurate results.