Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by azukhrufy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

update_doc_blocks

Update content blocks in a ClickUp Doc by specifying block IDs and new values for type, content, or attributes. Enables precise modifications without rewriting the entire document.

Instructions

Update content blocks in a ClickUp Doc.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>",
      "doc_id": "<doc_id>",
      "blocks": "<blocks>"
    },
    "name": "update_doc_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
blocksYesArray of block objects to update
doc_idYesThe ID of the doc
team_idYesThe ID of the team (workspace)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It only says 'Update content blocks' without covering whether the update is partial or full replacement, permission requirements, side effects, or error behavior. This is insufficient for a mutation tool.

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 a single, well-formed sentence with no redundant words. It conveys the core purpose efficiently, though it could include more detail without becoming verbose.

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

Completeness2/5

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

No output schema, no annotations, and a minimal description. The tool operates on a nested block array, but the description does not clarify the update semantics (e.g., replace entire block or merge), return behavior, or required permissions. This is incomplete for a non-trivial mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with each parameter (blocks, doc_id, team_id) clearly described. The tool description adds no extra parameter context, but the baseline of 3 applies since the schema handles parameter documentation.

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 'Update' and the resource 'content blocks in a ClickUp Doc'. It distinguishes from sibling tools like create_doc_blocks and delete_doc_blocks by indicating modification of existing blocks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that create_doc_blocks should be used for new blocks or delete_doc_blocks for removal, leaving the agent to infer from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools