Skip to main content
Glama
mondaycom

monday MCP Server

Official

Manage monday Platform Agent Triggers

manage_agent_triggers

List, add, or remove triggers that define when a monday.com agent runs automatically. Use block_reference_id to add trigger types and node_id to remove instances.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes"list" — returns all triggers currently attached to this agent (includes node_id needed for remove). "add" — attaches a new trigger by block_reference_id. "remove" — detaches a trigger instance by node_id.
agent_idYesUnique identifier of the agent.
block_reference_idNoRequired for action:"add". The block_reference_id from agent_catalog action:"list_triggers" identifying the trigger type to attach. Never guess this value — look it up in the catalog first.
field_valuesNoUsed with action:"add" when the trigger type has required_fields. Key/value object whose shape is described by field_schemas in the agent_catalog response. Scalar fields use string/number/boolean values. Selection fields use { "value": "<id>", "label": "<name>" }.
node_idNoRequired for action:"remove". The node_id of the trigger instance — get it from action:"list". Each instance has a unique node_id even if the same trigger type is attached multiple times. Do NOT pass block_reference_id here.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses that add returns only { success } and no node_id, requiring a follow-up list call. Also states OAuth triggers cannot be managed here. No contradiction with annotations (readOnlyHint=false, etc.).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections (ACTIONS, WORKFLOW, NOTE, USAGE EXAMPLES, RELATED TOOLS). Concise yet comprehensive, front-loading essential info.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all actions, exceptions, workflows, and returns despite no output schema. Fully adequate for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: explains block_reference_id must not be guessed, field_values shape with scalar vs selection fields, and distinction between node_id and block_reference_id for remove.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool manages agent triggers with three actions (list, add, remove). It distinguishes from related tools like manage_agent_skills and manage_agent. The title and description are aligned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit workflows for adding and removing triggers, including prerequisites (agent_catalog for add, list for remove). Also notes when not to use (OAuth/3rd-party triggers). Clear alternatives provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mondaycom/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server