Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom

Read Documents

read_docs
Read-onlyIdempotent

Fetch monday.com document content with markdown or view version history. Retrieve block details, comments, and content diffs with pagination support.

Instructions

Get information about monday.com documents. Supports two modes:

MODE: "content" (default) — Fetch documents with their full markdown content.

  • Requires: type ("ids" | "object_ids" | "workspace_ids") and ids array

  • Supports pagination via page/limit. Check has_more_pages in response.

  • If type "ids" returns no results, automatically retries with object_ids.

  • Set include_blocks: true to include block IDs, types, and positions in the response — required before calling update_doc.

  • Blocks default to 25 per page. Use blocks_limit and blocks_page to paginate through long documents.

  • Set include_comments: true to fetch all comments and replies on the document. Each comment is enriched with anchor info (block_id, selection_from, selection_length) indicating which block and text range it's attached to. Use comments_limit to control how many comments per item (default 50).

MODE: "version_history" — Fetch the edit history of a single document.

  • Requires: ids with the document's object_id (use the object_id field from content mode results, NOT the id field).

  • The object_id is the numeric ID visible in the document URL.

  • Returns restoring points sorted newest-first. Use version_history_limit to cap results (e.g., "last 3 changes" → version_history_limit: 3).

  • Use since/until to filter by time range. If omitted, returns full history.

  • Set include_diff: true to see what content changed between versions (fetches up to 10 diffs, may be slower).

  • Examples:

    • { mode: "version_history", ids: ["5001466606"], version_history_limit: 3 }

    • { mode: "version_history", ids: ["5001466606"], since: "2026-03-11T00:00:00Z", include_diff: true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoThe operation mode. "content" (default) fetches documents with their markdown content. "version_history" fetches the edit history of a single document.content
typeNoQuery type for content mode: "ids", "object_ids", or "workspace_ids". Required when mode is "content".
idsNoArray of ID values. In content mode: matches the query type (ids/object_ids/workspace_ids). In version_history mode: provide the single document object_id here (e.g., ids: ["5001466606"]).
limitNoNumber of docs per page (default: 25). Only used in content mode.
order_byNoOrder in which to retrieve docs. Only used in content mode.
pageNoPage number to return (starts at 1). Only used in content mode.
include_blocksNoIf true, includes the blocks array (block IDs, types, positions, content) in the response. Required when you plan to call update_doc. Defaults to false to reduce response size. Only used in content mode.
blocks_limitNoMaximum number of blocks to return per document (default: 25). Only used in content mode when include_blocks is true.
blocks_pageNoPage number for block pagination, starting at 1. Omit to use the API default. Use with blocks_limit to page through documents with more than 25 blocks. Only used in content mode when include_blocks is true.
include_commentsNoIf true, fetches all comments and replies on the document. Comments are stored at the item level within the doc backing board. Defaults to false. Only used in content mode.
comments_limitNoMaximum number of comments (updates) to fetch per item when include_comments is true. Defaults to 50. Only used in content mode.
version_history_limitNoMaximum number of restoring points to return. Use this when the user asks for "last N changes". Only used in version_history mode.
sinceNoISO 8601 date string to filter version history from (e.g., "2026-03-15T00:00:00Z"). If omitted, returns the full history. Only used in version_history mode.
untilNoISO 8601 date string to filter version history until (e.g., "2026-03-16T23:59:59Z"). Defaults to now. Only used in version_history mode.
include_diffNoIf true, fetches content diffs between consecutive restoring points. May be slower due to additional API calls. Only used in version_history mode.
Behavior5/5

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

The description discloses key behaviors beyond annotations: automatic retry of object_ids when ids returns no results, pagination defaults, mode-specific parameter requirements, and performance implications for include_diff. Annotations declare readOnlyHint=true, which aligns with the read nature, and no contradictions are present.

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-organized with mode headers, bullet points, and examples, making it easy to scan. It is thorough without being overly verbose, though the length could be slightly reduced by removing some redundancy in parameter explanations.

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?

Given the high parameter count (15), lack of output schema, and the tool's complexity (two modes, pagination, optional features), the description covers all necessary details: mode-specific requirements, parameter interdependencies, default behaviors, and practical examples. No gaps remain.

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%, but the description adds substantial value beyond the schema: it explains the object_id vs id distinction for version_history, provides examples, clarifies auto-retry behavior, and gives context for default values like blocks_limit and comments_limit. This extra context justifies a score above the baseline of 3.

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 gets information about monday.com documents and specifies two distinct modes ('content' and 'version_history'), providing a specific verb+resource combination. It distinguishes from sibling tools like 'update_doc' by mentioning block requirements for that tool.

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 is given for when to use each mode, required parameters, pagination, and important notes like the automatic retry for 'ids' type in content mode and the need for 'include_blocks' before calling 'update_doc'. This provides clear decision-making context for the agent.

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