monday.com

Activate a sequence. Changes status from INACTIVE to ACTIVE, enabling enrollment and step execution.

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_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 get_graphql_schema and get_type_details tools 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 to understand the board metadata. 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.

[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 to understand the board metadata. This is essential for constructing valid column values. For board-relation linking tasks, call link_board_items_workflow before using this tool.

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')"

Create a personal/custom agent on the monday.com platform. See get_agent for what a monday platform agent is.

Terminology note: users might ask for "agent" in natural language (for example: "create me an agent"), but in this API context this refers to monday personal/custom agents.

Two modes:

• Prompt mode (recommended): pass prompt (and optional agent_model) and the platform generates profile + goal + plan via AI.
• Manual mode: omit prompt and pass any of name/role/role_description/user_prompt to create a blank agent profile quickly.

Do not mix prompt with manual profile fields in one request.

Created agents start in state INACTIVE and must be activated before they can be triggered. Instruct the user to activate from the monday.com agent settings UI.

created_at and updated_at are null in the response — call get_agent with the returned id afterward to fetch them.

USAGE EXAMPLES:

• AI-generated: { "prompt": "Run my daily standup — collect status updates, summarize blockers, and post recap every weekday at 9am." }
• Blank/manual: { "name": "Standup Bot", "role": "Project Manager", "gender": "female" }
• Blank/defaults: {}

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

Create a new column in a monday.com board

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

[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 to understand the board metadata. 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 to understand the board metadata. 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. This creates a saved view on a monday.com board that users can switch to.

Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

Example filter for people column: { "rules": [{ "column_id": "people", "compare_value": ["person-12345"], "operator": "any_of" }] } Example filter for status column: { "rules": [{ "column_id": "status", "compare_value": [1], "operator": "any_of" }] }

Create a new table-type board view with optional filters, sort, tags, and table-specific settings (column visibility/order and group-by). Use this instead of create_view when you need to configure table-specific settings. For a simple table view, create_view also works.

Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

Example settings.columns: { "column_properties": [{ "column_id": "status", "visible": true }], "column_order": ["name", "status", "date"] } Example settings.group_by: { "conditions": [{ "columnId": "status" }], "hideEmptyGroups": true }

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.

Create a new workspace in monday.com

Creates a new sequence on a board. Always created INACTIVE — use activate-sequence to enable after creation.

CALL THIS TOOL DIRECTLY with whatever arguments you have. Do NOT call get-board-sequences, get-connected-email-accounts, or any other tool first — the gates below will tell you exactly what to do if anything is missing.

GATES (return CONFIRMATION_REQUIRED, nothing created): • board_not_specified — board_id omitted. • steps_not_specified — steps omitted. • connections_not_specified — timeline has automatic_email with sender/emailColumnId missing. Each gate response includes instructions for the next turn — follow them verbatim.

STEP TYPES: • { type: "manual_task_reminder" | "manual_call_reminder" | "manual_email_reminder", subject, body } — no sender/emailColumnId needed. • { type: "automatic_email", subject, body } — requires sender + emailColumnId. Omit trackingEnabled/isEmailThreaded unless the user asks (defaults: both on). • { type: "wait", days: N } (N ≥ 1) — gap before the next step; not a real step. Two consecutive steps with no wait run on the same day. A wait at the START delays the first step past day 1.

Never set ordinals or UUIDs. Never fabricate steps.

Create a new structured activity entry on a CRM item's timeline. Returns the created timeline_item_id. For freeform notes (meeting outcomes, follow-ups), use create-timeline-note instead.

Log a freeform text note on a CRM item's timeline — meeting outcomes, follow-up reminders, context for the next rep, or any unstructured observation.

Deactivate a sequence. Changes status from ACTIVE to INACTIVE, blocking new enrollments. Items already enrolled continue their execution.

Delete a saved action.

Example: id: "550e8400-e29b-41d4-a716-446655440000"

Permanently delete a personal/custom agent on the monday.com platform. Removes the agent and all of its versions. The agent stops appearing in get_agent results and can no longer be triggered. This action cannot be undone. Only the agent owner can delete it.

Terminology note: users might ask for "agent" in natural language (for example: "delete my standup agent"), but in this API context this refers to monday personal/custom agents.

VERIFY BEFORE DELETING: When the user refers to an agent by name or description (e.g. "delete my standup bot"), call get_agent (no id) first to list all the user's agents and confirm the correct id. Do not infer ids — pick the matching agent by inspecting profile.name / role / goal.

USAGE EXAMPLE: { "id": "42" }

Duplicate a sequence. Creates a copy with the same steps and configuration. The new sequence starts with INACTIVE status.

Enroll one or more CRM contacts or leads into an outreach sequence. The sequence must be active. Returns per-item success/failure so partial failures do not silently drop contacts.

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

Retrieve a saved action by ID.

Example: id: "550e8400-e29b-41d4-a716-446655440000"

Fetch one or more personal/custom agents on the monday.com platform.

monday platform agents are user-built work orchestrators and executors that live on the monday.com platform — each has a profile (name, role, avatar), a goal, and an execution plan in markdown describing capabilities and operating principles. Agents in state ACTIVE can be triggered to perform automated work on monday boards. They are NOT local LangChain or MCP agents — they are managed entities on the monday.com platform owned by a specific user.

Terminology note: users might ask for "agent" in natural language (for example: "create me an agent"), but in this API context this refers to monday personal/custom agents.

Agent state in get_agent results is one of ACTIVE, INACTIVE, ARCHIVED, or FAILED. DELETED agents are filtered from these queries — DELETED only appears as the return value of delete_agent. Agent kind is one of PERSONAL, ACCOUNT_LEVEL, or EXTERNAL.

Pass id to fetch one specific agent by its unique identifier. Omit id to list agents owned by the authenticated user (capped at 100 — ask the user for a higher limit if needed). An empty list means the user owns no agents, which is not an error.

USAGE EXAMPLES:

• Fetch one agent: { "id": "42" }
• List my agents: {}

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.

Get a presigned URL to upload a file to monday.com. Returns an upload_id and upload_url.

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.

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.

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.

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.

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.

Retrieves comprehensive information about a specific column type. Use fetchMode "schema" (default) to get the JSON schema definition from the API — use this before creating or updating columns (e.g. create_column) to understand structure, validation rules, and available properties for column settings. Use fetchMode "guidelines" to get only guidelines.filter and guidelines.aggregation for building items_page filters and board insights counts (no schema, no GraphQL round-trip).

Get a monday.com form by its form token. 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.

INTERNAL USE ONLY

• DO NOT CALL THIS TOOL DIRECTLY. This tool is exclusively triggered by UI components and should never be invoked directly by the agent.

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.

Retrieve notetaker meetings with optional detailed fields. Use include_summary, include_topics, include_action_items, and include_transcript flags to control which details are returned. Use access to filter by meeting access level (OWN, SHARED_WITH_ME, SHARED_WITH_ACCOUNT, ALL). Defaults to OWN. Supports filtering by ids, search term, and cursor-based pagination.

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

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 comprehensive sprint metadata from a monday-dev sprints board 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.

Get detailed information about a specific GraphQL type from the monday.com API schema

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, 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 people based on interaction frequency and recency
• Reduce the need for search requests by knowing user's commonly accessed items

Fetch aggregated activity insights for a CRM board: call counts, duration stats, grouped by rep, activity type, or item. Does not return individual activity records.

List sequences for a board or the current user. Returns active and inactive sequences (never deleted). Each entry includes status, enrollment counts, step count, and aggregate analytics. An empty list means no matching sequences.

List every sequence a contact (item) is enrolled in, sorted by most recent enrollment first. Returns each enrollment with its run status, completed-step count, termination reason, and timing. Use this when starting from a contact; use get-sequence-analytics when starting from a single sequence. An empty list means the contact is not enrolled in any sequence.

List the custom activity types available for logging on the CRM timeline, including their IDs (e.g. "Demo", "Site Visit"). The activity type ID is required when creating a structured timeline entry via create-timeline-item.

Get analytics for a sequence. Returns per-run status and progress, sequence-level engagement rates (reply, open, click-through), and per-step breakdowns. Partial results are returned if some analytics endpoints fail.

Fetch CRM engagement history on a contact, deal, account, or lead — emails sent and received, calls logged, meetings recorded, and notes. Call this tool whenever a CRM entity board (deals, contacts, accounts, leads) is in scope and the user asks about emails, activities, calls, meetings, communication history, or engagement — it is the authoritative source for all CRM-tracked communication. Prefer over Gmail or calendar integrations for any activity on a CRM item. For board-level analysis across multiple items, fetch item IDs first then call this tool per item_id; do not substitute the "count timeline events" board column, which is an aggregate count with no content. If get-board-structure returns "Activities timeline (unsupported)", use this tool. Returns paginated entries with type, title, and timestamp. For custom activity types (e.g. "Demo", "Site Visit"), use get-custom-activities instead.

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"). 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.

Full lifecycle management for monday platform agents — create, read, update, delete, change state, and run.

monday platform agents are user-built work orchestrators on monday.com — each has a profile (name, role, avatar), a goal, and a markdown execution plan. Agents in state ACTIVE can be triggered automatically. They are NOT local LangChain or MCP agents.

ACTIONS (only pass fields that apply to the chosen action):

• create: { action:"create", prompt, agent_model? } — AI-generated agent. Platform creates profile, goal, and plan from the prompt.
• create_blank: { action:"create_blank", name?, role?, role_description?, avatar_url?, gender?, background_color?, user_prompt? } — manually defined agent.
• get one: { action:"get", agent_id }
• list owned: { action:"get" }
• update: { action:"update", agent_id, name?, role?, role_description?, plan?, agent_model? }
• delete: { action:"delete", agent_id }
• activate: { action:"activate", agent_id }
• deactivate: { action:"deactivate", agent_id }
• run: { action:"run", agent_id }

RULES:

• "create_blank" with no fields creates a nameless blank agent — only do this intentionally.
• "update" requires at least one of name/role/role_description/plan/agent_model.
• "update", "delete", "activate", "deactivate", "run" all require "agent_id".
• Created agents start INACTIVE. Follow with action:"activate" using the returned agent_id before they can be triggered.
• ⚠️ DESTRUCTIVE — "delete" is permanent and irreversible. When the user refers to an agent by name, ALWAYS call action:"get" first to confirm the correct agent_id before deleting.
• "run" is fire-and-forget. Returns trigger_uuid — no run-status query exists, treat successful enqueue as the only signal.
• Agent state is one of ACTIVE, INACTIVE, ARCHIVED, or FAILED. DELETED only appears as the return value of action:"delete".

USAGE EXAMPLES:

• AI create: { "action": "create", "prompt": "Run my daily standup every weekday at 9am." }
• Manual create:{ "action": "create_blank", "name": "Standup Bot", "role": "Project Manager", "gender": "female" }
• Fetch one: { "action": "get", "agent_id": "42" }
• List mine: { "action": "get" }
• Rename: { "action": "update", "agent_id": "7", "name": "New Name" }
• Activate: { "action": "activate", "agent_id": "7" }
• Deactivate: { "action": "deactivate", "agent_id": "7" }
• Run: { "action": "run", "agent_id": "7" }
• Delete: { "action": "delete", "agent_id": "7" }

RELATED TOOLS:

• agent_catalog — browse available trigger types and skills before wiring them to an agent
• manage_agent_triggers — manage which triggers fire this agent automatically
• manage_agent_skills — manage which skills this agent can perform
• manage_agent_knowledge — manage which boards/docs this agent has access to

List, grant, update, or revoke a monday platform agent's access to boards and docs.

An agent's "knowledge" is the set of monday.com boards and docs it can read from or write to during a run.

• list: Returns all resources the agent currently has access to, including permission level and resource type.
• add: Grants the agent access to a board or doc with the specified permission level.
• update: Changes the permission level on a resource the agent already has access to. Call action:"list" first to confirm the resource_id exists.
• remove: Revokes the agent's access to a board or doc entirely. Call action:"list" first to confirm the resource_id exists.

Permission types:

• READ: Agent can read data from the resource.
• READ_WRITE: Agent can read and write data to the resource.

USAGE EXAMPLES:

• List: { "action": "list", "agent_id": "7" }
• Add board access: { "action": "add", "agent_id": "7", "resource_id": "42", "scope_type": "BOARD", "permission_type": "READ" }
• Update to read-write: { "action": "update", "agent_id": "7", "resource_id": "42", "scope_type": "BOARD", "permission_type": "READ_WRITE" }
• Remove access: { "action": "remove", "agent_id": "7", "resource_id": "42", "scope_type": "BOARD" }

RELATED TOOLS:

• manage_agent — manage the agent entity itself (create, activate, deactivate, etc.)
• manage_agent_triggers — manage which triggers fire this agent automatically
• manage_agent_skills — manage which skills this agent can perform

Manage the full skill lifecycle for monday platform agents — create new skills in the catalog, attach skills to an agent, or detach them.

Skills extend what an agent can do (e.g. sending emails, querying databases, posting to Slack).

ACTIONS:

• create: { name, content, description? } — creates a new custom skill in the account-wide catalog.

The skill becomes available to all agents in the account.

• add: { agent_id, skill_id } — attaches a skill to this agent.
• remove: { agent_id, skill_id } — detaches a skill from this agent.

WORKFLOW — attach an existing skill: 1. Call agent_catalog action:"list_skills" — find the skill_id of the skill to attach. 2. Call this tool action:"add" with agent_id and that skill_id.

WORKFLOW — create a new skill and attach it: 1. Call this tool action:"create" with name and content — note the returned id. 2. Call this tool action:"add" with agent_id and that id directly (no catalog lookup needed).

NOTE: There is no action to list which skills are currently attached to a specific agent — the platform does not yet expose that query. To browse all skills available in the account catalog, use agent_catalog action:"list_skills".

USAGE EXAMPLES:

• Create a skill: { "action": "create", "name": "Send Slack Message", "content": "

Instructions\nPost a message to a Slack channel.", "description": "Sends a message to Slack" }

• Add a skill: { "action": "add", "agent_id": "7", "skill_id": "skill-abc-123" }
• Remove a skill: { "action": "remove", "agent_id": "7", "skill_id": "skill-abc-123" }

RELATED TOOLS:

• agent_catalog action:"list_skills" — browse existing skills to find a skill_id before calling action:"add"
• manage_agent_triggers — manage which triggers fire this agent automatically
• manage_agent — manage the agent entity itself (create, activate, deactivate, etc.)

Manage the triggers attached to a monday platform agent — triggers define WHEN the agent runs automatically.

ACTIONS:

• list: { agent_id } — returns active triggers with node_id, block_reference_id, name, field_summary.
• add: { agent_id, block_reference_id, field_values? } — attaches a trigger type to the agent.
• remove: { agent_id, node_id } — detaches a trigger instance by node_id (NOT block_reference_id).

WORKFLOW — add a trigger: 1. Call agent_catalog action:"list_triggers" — note block_reference_id, field_schemas, and required_fields. 2. Collect required field values from the user (e.g. board_id, column_id). 3. Call this tool action:"add" with block_reference_id and field_values. Note: add returns only { success } — no node_id for the new instance. Call action:"list" afterward if you need the node_id.

WORKFLOW — remove a trigger: 1. Call action:"list" to see active triggers and note the node_id of the instance to remove. 2. Call action:"remove" with that node_id.

NOTE: Only triggers that can be added programmatically appear in the catalog. OAuth/3rd-party triggers (Slack, Gmail, Salesforce, etc.) require user setup in the monday.com UI — they will not appear in agent_catalog and cannot be managed here.

USAGE EXAMPLES:

• List triggers: { "action": "list", "agent_id": "7" }
• Add trigger: { "action": "add", "agent_id": "7", "block_reference_id": "status-change-ref", "field_values": { "board_id": "42" } }
• Remove trigger: { "action": "remove", "agent_id": "7", "node_id": "node-abc" }

RELATED TOOLS:

• agent_catalog action:"list_triggers" — discover available trigger types and their required field_values before calling action:"add" here
• manage_agent_skills — manage which skills this agent can perform
• manage_agent — manage the agent entity itself (create, activate, deactivate, etc.)

Activate, deactivate, or delete an existing monday.com automation.

Requires an automation id. When the user refers to an automation by name, always call list_automations first to resolve the id — never guess or infer ids.

Actions:

• activate: enables a paused automation so it starts responding to its trigger.
• deactivate: pauses an automation while preserving its definition.
• delete: permanently removes an automation — irreversible.

When intent is ambiguous ("stop", "turn off", "pause"), prefer deactivate over delete.

Activate, deactivate, or delete an existing monday.com automation/workflow.

Requires a workflow id. When the user refers to an automation by name, always call list_automations first to resolve the id — never guess or infer ids.

Actions:

• activate: enables a paused workflow so it starts responding to its trigger.
• deactivate: pauses a workflow while preserving its definition.
• delete: permanently removes a workflow — irreversible.

When intent is ambiguous ("stop", "turn off", "pause"), prefer deactivate over delete.

Terminology: "workflows" and "automations" are the same thing.

Move a folder, board, or overview in monday.com. Use position for relative placement based on another object, parentFolderId for folder changes, workspaceId for workspace moves, and accountProductId for account product changes.

Promotes a workflow draft to live and optionally activates it.

Use this tool when the user asks to publish, go live, or activate a workflow. The workflow is validated before publishing; if it has unresolved validation issues, the tool returns those issues instead of publishing, so they can be reported back to the user and fixed first.

On success, the tool returns a JSON object with the workflowObjectId and the resulting workflowLiveId.

Get information about monday.com documents. Supports two modes:

MODE: "content" (default) — Fetch documents with their full markdown content.

• Requires: type ("ids" | "object_ids" | "workspace_ids") and ids array
• Supports pagination via page/limit. Check has_more_pages in response.
• If type "ids" returns no results, automatically retries with object_ids.
• Set include_blocks: true to include block IDs, types, and positions in the response — required before calling update_doc.
• Blocks default to 25 per page. Use blocks_limit and blocks_page to paginate through long documents.
• Set include_comments: true to fetch all comments and replies on the document. Each comment is enriched with anchor info (block_id, selection_from, selection_length) indicating which block and text range it's attached to. Use comments_limit to control how many comments per item (default 50).

MODE: "version_history" — Fetch the edit history of a single document.

• Requires: ids with the document's object_id (use the object_id field from content mode results, NOT the id field).
• The object_id is the numeric ID visible in the document URL.
• Returns restoring points sorted newest-first. Use version_history_limit to cap results (e.g., "last 3 changes" → version_history_limit: 3).
• Use since/until to filter by time range. If omitted, returns full history.
• Set include_diff: true to see what content changed between versions (fetches up to 10 diffs, may be slower).
• Examples:
• { mode: "version_history", ids: ["5001466606"], version_history_limit: 3 }
• { mode: "version_history", ids: ["5001466606"], since: "2026-03-11T00:00:00Z", include_diff: true }

Execute a saved action by ID. Optionally pass variables (injected as environment variables, access via os.environ).

Example: id: "abc-123", vars: {"board_id": 12345, "limit": 5}

Search within monday.com platform. Supported searchType values: BOARD, DOCUMENTS, FOLDERS, WORKSPACES, UPDATES, ITEMS, TIMELINE_ITEMS, DASHBOARDS. searchTerm is the phrase the search matches against — the text/keywords to look for (e.g. a board name, item title, or a word from an update). It is required and must be non-empty. This tool has no "list everything" mode: to browse or list without a search phrase, use workspace_info (boards/docs/folders in a workspace) or get_board_items_page (items in a board) instead of calling search with an empty searchTerm. For searching/listing specific users and teams, use list_users_and_teams tool. For account-level info (plan, member count, products), use get_user_context tool. For browsing all boards, docs, or folders within a workspace without a search term, use workspace_info tool. For groups, use get_board_info tool. For listing items within a specific board, use get_board_items_page tool. ITEMS search here queries items across the account. BOARD search returns id, title, url, and workspaceId. Optionally scope it with boardIds. DOCUMENTS search returns id, title, and workspaceId. ITEMS search returns id, title, url, boardId, and workspaceId. Optionally scope it with workspaceIds, boardIds, and/or creatorIds. WORKSPACES search returns id, title, and description. UPDATES search returns id, title (the update body), itemId, boardId, and creatorId. Optionally scope it with boardIds and/or creatorIds. TIMELINE_ITEMS search returns id, title, summary, content, itemId, and boardId. Optionally scope it with boardIds. DASHBOARDS search (also called "overviews") returns id, title, and workspaceId. Optionally scope it with workspaceIds and/or creatorIds. FOLDERS search returns id and title. Optionally scope it with workspaceIds, which searches all accessible workspaces when omitted. Pass workspaceIds to narrow the search if results may be truncated.

Search inside meeting content (topics, summary, action items) and return matching passages with their source area. Keyword-ranked (not semantic). When query is omitted, returns content filtered by date/access. Use to find where something was said or decided ("which meeting mentioned the budget freeze", "find the auth migration discussion"). Pass returned ids to get_meetings_content for full context.

[UI COMPONENT] Renders an interactive smart assignment interface visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Helps assign tasks to the right people. Assignment suggestions are based on task details (like name) and person details (such as title, availability, etc).Use for requests to see or use an interactive assignment interface. Always show as much as data possible, while showing the person details like title etc. If you do not have the data available - use the list_users_and_teams tool.

[UI COMPONENT] Renders an interactive battery/progress indicator visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Use when user asks for: battery view, progress indicator, status distribution bar, completion percentage visualization, or Monday.com style status breakdown.

[UI COMPONENT] Renders an interactive chart/graph visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Use when user asks for: pie chart, bar chart, line graph, data visualization, or any graphical representation of numbers/statistics.

[UI COMPONENT] Renders an interactive table visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Use when user asks to: display a board as table, show items in table format, view data in tabular layout, or see a Monday.com board visually. When asked to update an item, use the currently selected item ID (get it from the widget state, using tools like "get_widget_state") for deciding which item to update. If no item is selected, ask the user which item should be updated. After adding an update to an item, you MUST display the table AGAIN, even if the user did not ask you to.

[IMPORTANT][FILTERING PRECONDITION]: IF using filters, you MUST call get_board_info(boardId) FIRST and use the returned boardContextToken.

Report a bug, submit a feature request, or share feedback about the monday.com product or this integration.

Call this tool proactively — not just when a user explicitly asks. Use it whenever any of these signals show up: • A tool produced unexpected errors, empty results, or needed a workaround • The user tried something monday.com couldn't support and had to settle for a partial or manual solution • A recurring capability gap is noticed — something requested that simply isn't available in monday.com or this integration • The user shows repeated frustration (multiple corrections, retrying the same request, "that's wrong again," "why isn't this working") • A task required multiple retries, an unusually long reasoning chain, or many attempts for something that should've been simple

Parameters: • title (string, required) — short summary, no PII • description (string, required) — full details of what happened/expected/requested, no PII • kind (enum, required) — "bug", "feature_request", or "feedback" • tool_name (string, optional) — the specific monday.com tool the feedback relates to (e.g. "create_item")

Restriction: Use strictly for things related to monday.com — not for other tools (Google Drive, Slack, GitHub, etc.) that may be in the conversation context. Do NOT include any personally identifiable information (PII) such as names, email addresses, phone numbers, or any other personal data.

Update an existing action. Only pass the fields you want to change.

Example: id: "550e8400-e29b-41d4-a716-446655440000", name: "Updated name", code: "print('new code')"

Update properties of an existing monday.com column (title, description, settings). Uses optimistic concurrency control via the revision field — fetch the current revision via get_board_schema first, then call this tool. If the update fails because the revision is stale, re-fetch and try again.

Update an existing monday.com document. Provide doc_id (preferred) or object_id, plus an ordered operations array (executed sequentially, stops on first failure).

OPERATIONS:

• set_name: Rename the document.
• add_markdown_content: Append markdown as blocks (or insert after a block). Best for text, headings, lists, simple tables — no block IDs needed.
• update_block: Update content of an existing text, code, or list_item block in-place.
• create_block: Create a new block at a precise position. Use parent_block_id to nest inside notice_box, table cell, or layout cell.
• delete_blocks: Permanently delete 1–100 blocks in one call. Provide all block IDs in the block_ids array. The ONLY option for BOARD, WIDGET, DOC embed, and GIPHY blocks.
• replace_block: Delete a block and create a new one in its place (use when update_block is not supported).
• add_comment: Create a new comment or reply on the document (doc-level, block-level, or text-selection).

WHEN TO USE EACH OPERATION:

• text / code / list_item → update_block. Use replace_block to change subtype (e.g. NORMAL_TEXT→LARGE_TITLE)
• divider / table / image / video / notice_box / layout → replace_block (properties immutable after creation)
• BOARD / WIDGET / DOC / GIPHY → delete_blocks only

GETTING BLOCK IDs: Call read_docs with include_blocks: true — returns id, type, position, and content per block.

BLOCK CONTENT (delta_format): Array of insert ops. Last op MUST be {insert: {text: "\n"}}.

• Plain: [{insert: {text: "Hello"}}, {insert: {text: "\n"}}]
• Bold: [{insert: {text: "Hi"}, attributes: {bold: true}}, {insert: {text: "\n"}}]
• Mention user/doc/board: [{insert: {text: "Hey "}}, {insert: {mention: {id: 12345, type: "USER"}}}, {insert: {text: "\n"}}] — type is USER, DOC, or BOARD. id is numeric (user IDs from list_users_and_teams)
• Inline column value: [{insert: {column_value: {item_id: 111, column_id: "status"}}}, {insert: {text: "\n"}}]
• Supported attributes: bold, italic, underline, strike, code, link, color, background (not applicable to mention/column_value ops)

IMAGE WITH ASSET: For asset-based images, use create_block with block_type "image" and asset_id (instead of public_url). add_markdown_content does NOT support asset images — for mixed content, alternate add_markdown_content (text) and create_block (image) operations in sequence.

BATCHING DELETES: delete_blocks accepts 1..100 IDs. Put ALL IDs in one operation's block_ids array. Never emit multiple delete_blocks operations in a row.

COMMENTS:

• add_comment: Create a new comment or reply on the document. Three scopes:
• Doc-level (no block_id): comment appears on the doc as a whole.
• Block-level (block_id only): comment is anchored to a specific block. The block shows a comment indicator in the UI.
• Text-selection (block_id + selection_from + selection_length): comment is anchored to a specific character range inside a text/code/list_item block. That text is highlighted with a comment marker.

Block-level and text-selection comments only work on blocks with text content (text, code, list_item, title, quote). They do NOT work on: divider, page_break, table, layout, notice_box, image, video, or giphy blocks. Get block IDs from read_docs with include_blocks: true. Format body with HTML, not markdown. Use mentions_list for @mentions.

Update an existing folder in monday.com

Update a monday.com form. Use the action field to specify the operation.

Update column values for up to 40 items in a single call. Each update targets one item by itemId and sets one or more column values on it. Each update is independent - it can target its own board via boardId and set its own column values, so a single call can update many items across multiple boards, apply the same value to many items, or apply different values per item. Each update returns its own item_id and item_url on success or a raw error message on failure. To link board-relation columns, call link_board_items_workflow before using this tool. [REQUIRED PRECONDITION]: Before using this tool, if you are not familiar with the board structure (column IDs, column types, status labels), first use get_board_info to understand the board metadata. This is essential for constructing valid column values.

Update an existing board view (tab) — change its name, filter rules, or sort order. Provide only the fields you want to change. Omitted fields are left unchanged.

Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

Example filter for people column: { "rules": [{ "column_id": "people", "compare_value": ["person-12345"], "operator": "any_of" }] } Example filter for status column: { "rules": [{ "column_id": "status", "compare_value": [1], "operator": "any_of" }] }

Update an existing table-type board view — change its name, filters, sort, tags, or table-specific settings (column visibility/order and group-by). Provide only the fields you want to change. Omitted fields are left unchanged.

Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

Example settings.columns: { "column_properties": [{ "column_id": "status", "visible": true }], "column_order": ["name", "status", "date"] } Example settings.group_by: { "conditions": [{ "columnId": "status" }], "hideEmptyGroups": true }

Update an existing workspace in monday.com

Validates the current workflow's structure and step configuration. Reports issues such as a missing trigger or action block, a delay/wait-trigger block left as a leaf, an empty loop, unknown blocks, missing required inputs, type mismatches between a variable and the field it's bound to, cross-branch node-results references, or invalid variable values.

Use this tool when:

• The user asks "is my workflow ready?", "what's missing?", "can I publish?", "validate my workflow", or similar.
• After you finished structural changes, to confirm the user still has things to configure.
• Before suggesting the user publish/activate the workflow.

The tool does NOT modify the workflow. It only inspects the current state. The response is always a JSON object with an "issues" array; an empty array means the workflow is fully configured. Each issue has a "code" discriminator with code-specific fields, and (when applicable) is enriched with stepVisibleId, stepTitle, and blockName for human-readable context.

Ask a read-only question about an existing Vibe app. Blocks for up to 45s (configurable via timeout_ms) awaiting the assistant reply. Status: COMPLETED with the reply, TIMEOUT if the workflow did not finish in time (call vibe_get later to retrieve it), or FAILED if the workflow errored or was cancelled. Optional model to pick the LLM for the answer.

Creates a new Vibe app from a natural-language prompt. Returns immediately with app_id and editor_link — the URL of the Vibe builder/chat page for the new app (https://{accountSlug}.monday.com/vibe/app/{appId}); the user can open it right away to watch generation in progress. Generation itself runs asynchronously — poll vibe_get for status. Optional: board_ids to connect existing boards (omit to auto-create), view_id to host a dashboard widget, and model to pick the LLM.

Delete a Vibe app and its associated assets. Destructive.

Fetch a Vibe app by id. App metadata is always returned, including editor_link — the URL of the Vibe builder/chat page for this app (https://{accountSlug}.monday.com/vibe/app/{appId}); usable as soon as the app row exists. Pass include to add expensive slices: status (refreshes status + adds is_busy, default true), messages (with optional from_date), code_versions.

List Vibe apps owned by the authenticated user. Supports pagination, search, status, and is_published filters.

Manage the publication state of a Vibe app on the caller account. action=publish requires the app to be deployed and respects the published-apps license limit. action=unpublish removes the app from the account.

Sends a follow-up message to modify an existing app. Fire-and-forget — returns immediately with user_message_id and editor_link (the Vibe builder/chat URL for this app, https://{accountSlug}.monday.com/vibe/app/{appId}). Returns APP_BUSY (409) if the app is currently generating; poll vibe_get first. Optional model to pick the LLM for this build.

This tool returns the boards, docs and folders in a workspace and which folder they are in. It returns up to 100 of each object type, if you receive 100 assume there are additional objects of that type in the workspace.