Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom

Create Document

create_doc

Create a new document in a monday.com workspace or attach one to an item, then import markdown content into it.

Instructions

Create a new monday.com doc either inside a workspace or attached to an item (via a doc column). After creation, the provided markdown will be appended to the document.

LOCATION TYPES:

  • workspace: Creates a document in a workspace (requires workspace_id, optional doc_kind, optional folder_id, optional docOwnerIds)

  • item: Creates a document attached to an item (requires item_id, optional column_id, optional docOwnerIds)

USAGE EXAMPLES:

  • Workspace doc: { location: "workspace", workspace_id: 123, doc_name: "My Doc", doc_kind: "private" , markdown: "..." }

  • Workspace doc in folder: { location: "workspace", workspace_id: 123, doc_name: "My Doc", folder_id: 17264196 , markdown: "..." }

  • Item doc: { location: "item", item_id: 456, doc_name: "My Doc", column_id: "doc_col_1" , markdown: "..." }

  • Workspace doc with agent owner: { location: "workspace", workspace_id: 123, doc_name: "My Doc", markdown: "...", docOwnerIds: [""] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_nameYesName for the new document.
markdownYesMarkdown content that will be imported into the newly created document as blocks.
locationYesLocation where the document should be created - either in a workspace or attached to an item
docOwnerIdsNoOptional list of user IDs to set as document owners at creation time. Use this to add the agent owner so they retain access to the document. Ownership is set inside the creation mutation itself, bypassing the permission checks that would block a subsequent add_subscribers_to_object call.
workspace_idNo[REQUIRED - use only when location="workspace"] Workspace ID under which to create the new document
doc_kindNo[OPTIONAL - use only when location="workspace"] Document kind (public/private/share). Defaults to public.
folder_idNo[OPTIONAL - use only when location="workspace"] Optional folder ID to place the document inside a specific folder
item_idNo[REQUIRED - use only when location="item"] Item ID to attach the new document to
column_idNo[OPTIONAL - use only when location="item"] ID of an existing "doc" column on the board which contains the item. If not provided, the tool will create a new doc column automatically when creating a doc on an item.
Behavior5/5

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

Annotations indicate non-readonly, non-destructive, non-idempotent. The description adds behavioral details: creation is a mutation, markdown is appended, ownership is set via docOwnerIds bypassing permission checks. This exceeds annotation information.

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?

The description is well-structured with sections for location types and usage examples. It is substantive and front-loaded, but could be slightly more concise (e.g., examples could be condensed). Still, it earns its place without excessive verbosity.

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?

Given the complexity of 9 parameters with conditional requirements, the description covers both location scenarios thoroughly with examples and behavioral notes. It lacks mention of return value (e.g., doc ID), but this is minor and the description is otherwise complete.

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 the description adds value by grouping parameters by location, clarifying conditional requirements (e.g., 'use only when location="workspace"'), providing defaults (doc_kind defaults to public), and offering concrete usage examples. This goes well beyond the schema alone.

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 verb 'Create' and specifies the resource 'monday.com doc' with two distinct location types (workspace or item). It distinguishes from sibling tools like 'update_doc', 'read_docs', and 'add_content_to_doc' by focusing on creation.

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 guidance on when to use each location type, including required vs optional parameters per scenario. Usage examples illustrate typical input structures. However, it does not explicitly state when NOT to use this tool or mention alternatives like 'add_content_to_doc' for existing docs.

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