Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom

Manage monday Platform Agent Knowledge

manage_agent_knowledge

Manage an agent's access to monday.com boards and docs: list current resources, grant, update, or revoke permissions with read or read-write levels.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes"list" — returns all resources the agent currently has access to. "add" — grants access to a board or doc. "update" — changes the permission level on an existing resource. "remove" — revokes the agent's access to a board or doc.
agent_idYesUnique identifier of the agent.
resource_idNoRequired for action:add, action:update, action:remove. The ID of the board or doc to grant/update/revoke access to.
scope_typeNoRequired for action:add, action:update, action:remove. The type of resource: "BOARD" or "DOC".
permission_typeNoRequired for action:add and action:update. The permission level: "READ" (agent can read the resource) or "READ_WRITE" (agent can read and write the resource).
Behavior4/5

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false). The description discloses that actions include add, update, remove which are destructive, and explains the effect of each action (e.g., remove revokes access entirely). No contradiction 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.

Conciseness5/5

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

The description is well-structured with clear sections for actions, permission types, usage examples, and related tools. It is front-loaded with a summary and contains no unnecessary sentences.

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

Completeness3/5

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

No output schema exists. The description explains the return for 'list' (returns resources) but does not describe the return for add/update/remove. It also does not mention error handling or rate limits. Given the complexity and lack of output schema, the description is adequate but could be more complete.

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 description coverage is 100%, so the schema already documents parameters well. The description adds value by explaining the meaning of actions and permission types, providing usage examples, and clarifying which parameters are required for which actions.

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 access to boards and docs (list, grant, update, revoke). It defines 'knowledge' and distinguishes from sibling tools like manage_agent, 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 Guidelines4/5

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

The description provides explicit when-to-use for each action, including preconditions like calling 'list' first. Usage examples are given. However, it does not explicitly state when to avoid this tool (e.g., for managing the agent entity itself), though related tools imply alternatives.

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