Monday.com

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

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 a monday.com workspace. Use this when the user wants to build a new standalone workflow from scratch. Workflows are cross-board, workspace-level — distinct from automations (use create_automation for those). You only need a workspaceId to get started — all other fields are optional. Returns: - workflowObjectId: the workflow object ID - workflowDraftId: the current draft version ID — workflows start as drafts and must be published before they run Terminology: - Workflows vs. automations: workflows are standalone objects scoped to a workspace. Automations (create_automation) are per-board trigger/action rules. They are different products. - Draft: the editable, inactive version of a workflow. Changes are made on the draft version until it is published as the live version. - Privacy: PUBLIC — visible to all workspace members (default). PRIVATE — restricted access. SHAREABLE — accessible to guests outside the account. Note: if directing the user to the workflow in the UI, the correct URL path is custom_objects/, not workflows/ — e.g. {account}.monday.com/custom_objects/{workflowObjectId}.

Create a new workspace in monday.com

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

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.

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.

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.

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

List all automations on a specific monday.com board, including their ids, titles, active state, and configuration. When NOT to use: Do not call this tool to get general board information unrelated to automations. Note: Some legacy automations may not appear — mention this if users ask about missing 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.

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.