Problem
There is no way to set an item's description when creating an item. The only path is a two-step flow:
create_item — creates the item
all_monday_api with set_item_description_content — sets the description via raw GraphQL
The second step requires knowing that set_item_description_content exists at all, which means dumping and grepping the full GraphQL schema (51KB). In practice, LLM agents fall back to create_update instead — which creates an update (on the second task tab), not a description (on the first task tab).
Root cause
set_item_description_content was added to the Monday API on January 26, 2026 (v2026-04) and is not yet surfaced as a dedicated MCP tool.
Proposed fix
Add an optional description (markdown string) parameter to create_item. Internally, after creating the item, the tool calls set_item_description_content with the provided markdown.
This collapses a two-call, schema-diving workflow into a single obvious operation.
Alternatives considered
- A standalone
set_item_description tool — better than the current situation where agents use create_update, but doesn't solve the creation case
- Documenting the mutation in
all_monday_api's description — reduces the discoverability gap but doesn't fix the DX
Problem
There is no way to set an item's description when creating an item. The only path is a two-step flow:
create_item— creates the itemall_monday_apiwithset_item_description_content— sets the description via raw GraphQLThe second step requires knowing that
set_item_description_contentexists at all, which means dumping and grepping the full GraphQL schema (51KB). In practice, LLM agents fall back tocreate_updateinstead — which creates an update (on the second task tab), not a description (on the first task tab).Root cause
set_item_description_contentwas added to the Monday API on January 26, 2026 (v2026-04) and is not yet surfaced as a dedicated MCP tool.Proposed fix
Add an optional
description(markdown string) parameter tocreate_item. Internally, after creating the item, the tool callsset_item_description_contentwith the provided markdown.This collapses a two-call, schema-diving workflow into a single obvious operation.
Alternatives considered
set_item_descriptiontool — better than the current situation where agents usecreate_update, but doesn't solve the creation caseall_monday_api's description — reduces the discoverability gap but doesn't fix the DX