Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom

Create Item

create_item

Create items, subitems, or duplicate and update existing items on a monday.com board using specified column values and board structure.

Instructions

Create a new item with provided values, create a subitem under a parent item, or duplicate an existing item and update it with new values. Use parentItemId when creating a subitem under an existing item. Use duplicateFromItemId when copying an existing item with modifications.[REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info to understand the board metadata. This is essential for constructing proper column values and knowing which columns are available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesThe id of the board to which the new item will be added
nameYesThe name of the new item to be created, must be relevant to the user's request
groupIdNoThe id of the group id to which the new item will be added, if its not clearly specified, leave empty
columnValuesYesA string containing the new column values for the item following this structure: {\"column_id\": \"value\",... you can change multiple columns at once, note that for status column you must use nested value with 'label' as a key and for date column use 'date' as key} - example: "{\"text_column_id\":\"New text\", \"status_column_id\":{\"label\":\"Done\"}, \"date_column_id\":{\"date\":\"2023-05-25\"},\"dropdown_id\":\"value\", \"phone_id\":\"123-456-7890\", \"email_id\":\"test@example.com\"}"
parentItemIdNoThe id of the parent item under which the new subitem will be created
duplicateFromItemIdNoThe id of existing item to duplicate and update with new values (only provide when duplicating)
Behavior4/5

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

Annotations already indicate mutability (readOnlyHint=false). Description adds context about non-destructive creation and the prerequisite for board structure knowledge. 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?

Four sentences, front-loaded with purpose, then parameter usage and prerequisite. Every sentence is essential and well-structured.

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?

Covers the three modes and prerequisite well. Minor gap: no description of return value (e.g., created item ID) since output schema absent.

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%, baseline 3. Description adds value by explaining how to use parentItemId for subitems and duplicateFromItemId for duplication, and provides an example for columnValues beyond schema.

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 creates items with three modes: new item, subitem under parent, or duplicate with modifications. It distinguishes from sibling tools like delete_item and change_item_column_values.

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 guidance on when to use parentItemId vs duplicateFromItemId, and a prerequisite to use get_board_info if unfamiliar with board structure. Clearly differentiates from other tools.

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