Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom

Manage monday Platform Agent Skills

manage_agent_skills

Create custom skills and attach or detach them to manage agent capabilities.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes"create" — author a new custom skill in the account-wide catalog (no agent_id needed). "add" — attach an existing skill to this agent by skill_id. "remove" — detach a skill from this agent.
agent_idNoRequired for action:"add" and action:"remove". Not used for action:"create" (account-level operation).
nameNoRequired for action:"create". Display name of the new skill.
contentNoRequired for action:"create". Markdown instructions defining what the skill does and how to execute it. Be specific and thorough — this is the skill's runtime behavior.
descriptionNoUsed with action:"create". Short description shown in the catalog.
skill_idNoRequired for action:"add" and action:"remove". The skill id from agent_catalog action:"list_skills", or the id returned by action:"create" in this tool. Never guess or invent a skill id.
Behavior5/5

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

Description adds context beyond annotations: creating a skill is account-wide, and the platform does not yet expose a query to list attached skills. No contradictions with annotations.

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?

Well-structured with clear sections for actions, workflows, examples, and related tools. Slightly lengthy but justified given the complexity of the tool.

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

Completeness4/5

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

No output schema, but description provides examples and indicates return behavior (noted id). Mentions the limitation of missing 'list attached skills' action, which is helpful.

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 detailed explanations for each parameter, including conditional requirements and usage examples, making it highly informative.

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 it manages the full skill lifecycle (create, add, remove) and distinguishes from sibling tools like agent_catalog and manage_agent.

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?

Provides explicit workflows for attaching existing skills or creating and attaching new ones, and notes when to use agent_catalog instead. Includes a note about the missing 'list attached skills' action.

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