Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom

Add Content to Document

add_content_to_doc

Add markdown content to an existing monday.com document. Identify the document by doc_id or object_id, and optionally insert after a specific block.

Instructions

Add markdown content to an existing monday.com document.

IDENTIFICATION: Provide either doc_id or object_id to identify the document:

  • doc_id: The document ID (the id field returned by read_docs). Takes priority if both provided.

  • object_id: The document object ID (the object_id field from read_docs, also visible in the document URL). Will be resolved to a doc_id.

USAGE EXAMPLES:

  • By doc_id: { doc_id: "123", markdown: "# New Section\nContent here" }

  • By object_id: { object_id: "456", markdown: "# New Section\nContent here" }

  • Insert after block: { doc_id: "123", markdown: "Inserted content", after_block_id: "block_789" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idNoThe document ID (the id field returned by read_docs). Provide this OR object_id. Takes priority if both are provided.
object_idNoThe document object ID (the object_id field from read_docs, also visible in the document URL). Will be resolved to a doc_id. Provide this OR doc_id.
markdownYesMarkdown content to add to the document.
after_block_idNoBlock ID after which to insert the new content. If omitted, content is appended at the end. To insert at the beginning, pass the first block ID from read_docs. Block IDs can be obtained from read_docs or from a previous add_content_to_doc response.
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds context on how content is added (append or insert after a block) and resolution of object_id to doc_id. It does not cover idempotency or fail states, but adds value beyond 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 concise, well-structured with clear sections (identification, usage examples) and no wasted sentences. It effectively communicates key information.

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

Completeness5/5

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

Even without an output schema, the description covers identification, content insertion, and positioning. It is complete for a tool that adds content to a document, with no missing critical information.

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%, so baseline 3. The description adds value by explaining the priority between doc_id and object_id, and the meaning of after_block_id with examples. This goes beyond the schema descriptions.

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 'Add markdown content to an existing monday.com document.' This is a specific verb-resource pair that distinguishes it from siblings like create_doc (create new) and update_doc (modify settings).

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 detailed guidance on identifying the document via doc_id or object_id, with usage examples. It does not explicitly state when not to use this tool versus alternatives, but the context is clear for adding content.

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