Skip to main content
Glama
mondaycom

monday MCP Server

Official

Update Folder

update_folder
Idempotent

Update a folder's name, color, icon, font weight, parent folder, or position in monday.com.

Instructions

Update an existing folder in monday.com

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderIdYesThe ID of the folder to update
nameNoThe new name of the folder
colorNoThe new color of the folder
fontWeightNoThe new font weight of the folder
customIconNoThe new custom icon of the folder
parentFolderIdNoThe ID of the new parent folder
workspaceIdNoThe ID of the workspace containing the folder
accountProductIdNoThe account product ID associated with the folder
position_object_idNoThe ID of the object to position the folder relative to. If this parameter is provided, position_object_type must be also provided.
position_object_typeNoThe type of object to position the folder relative to. If this parameter is provided, position_object_id must be also provided.
position_is_afterNoWhether to position the folder after the object
Behavior3/5

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

Annotations indicate idempotent and non-destructive behavior, and the description adds no further behavioral context (e.g., permission requirements, side effects). This is adequate but not additive.

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?

A single, clear sentence with no redundant information. Every word earns its place.

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

Completeness2/5

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

With 11 parameters including conditional inter-dependencies (e.g., position_object_id/type) and no output schema, the description is too minimal to provide complete understanding of how the tool behaves.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already explains each parameter. The description adds no extra meaning beyond what's in the schema, achieving the baseline.

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

Purpose4/5

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

The description clearly states the tool updates an existing folder in monday.com, but does not distinguish it from sibling tools like create_folder or move_object that also modify folder properties.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives; for instance, moving a folder could also be done via move_object, but no comparison is 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