Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom

monday Platform Agent Catalog

agent_catalog
Read-onlyIdempotent

Browse the account-wide catalog of available trigger types and skills for monday platform agents. Discover what is available before wiring to a specific agent.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes"list_triggers" — fetch available trigger types with block_reference_id, field_schemas, and required_fields. Call before using manage_agent_triggers action:"add". "list_skills" — fetch available skills with id, name, description. Call before using manage_agent_skills action:"add".
block_reference_idsNoUsed with action:"list_triggers". Fetch specific trigger types by block_reference_id. Omit to return all trigger types.
Behavior5/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description reinforces this with 'READ-ONLY' and adds context about limitations (e.g., OAuth triggers not appearing) and the structure of returned data.

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

Conciseness4/5

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

The description is well-structured with clear sections (actions, examples, related tools) and is comprehensive. It could be slightly more concise, but all information is relevant and earns its place.

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?

Given the tool's two actions and relation to other tools, the description is complete. It explains return fields, limitations, and usage in conjunction with related tools. No output schema exists, so the description compensates by detailing response structure.

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

Parameters4/5

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

Schema coverage is 100% and schema property descriptions are thorough. The tool description adds value by explaining parameter usage (e.g., 'Never guess or invent a skill id') and providing examples. While already well-covered in schema, the description enhances understanding.

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's purpose: browsing the account-wide catalog of trigger types and skills for monday platform agents. It specifies the two actions (list_triggers and list_skills) and distinguishes from sibling tools like manage_agent_triggers and manage_agent_skills.

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 usage guidance is provided: 'Use this tool to discover what's available BEFORE wiring anything to a specific agent.' It also explains when not to use it (e.g., OAuth triggers) and gives related tools for further actions.

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