Skip to main content
Glama
rafadepaula

@rafadepaula/clickup-mcp

by rafadepaula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

clickup_update_document_page

Update a ClickUp document page's name, subtitle, or content, choosing replace, append, or prepend to control how new content is applied.

Instructions

Update a page in a ClickUp document. Use content_edit_mode to control how content is applied: append/prepend merge with the existing page server-side and preserve it exactly — no need to read the page first. The default is 'replace', which overwrites the whole page. If appended content should start on its own line, include a leading newline; if prepended content should end on its own line, include a trailing newline.

Input Schema

NameRequiredDescriptionDefault
nameNoNew name for the page
contentNoNew content for the page (must be non-empty; clearing a page is not supported). By default this REPLACES the entire existing page content — set content_edit_mode to 'append' or 'prepend' to add to the page instead of overwriting it.
page_idYesID of the page to update (e.g. 'ad-2675877'). In ClickUp doc URLs, this is the second ID after /docs/ or /v/dc/.
sub_titleNoNew subtitle for the page
document_idYesID of the document containing the page (e.g. 'ad-909705'). In ClickUp doc URLs, the document_id is always the first ID after /docs/ or /v/dc/.
workspace_idNoWorkspace ID (digits only). Only needed when you have multiple workspaces.
content_formatNoThe format of the page contenttext/md
content_edit_modeNoHow to apply `content`: 'append' adds it at the end of the existing page, 'prepend' inserts it before the existing content, 'replace' (default) OVERWRITES the entire page — existing content is lost. Ignored when `content` is not provided.replace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key destructive behavior: default replace overwrites the whole page, while append/prepend merge server-side and preserve existing content. It also gives newline semantics. It omits permission/workspace requirements and return behavior, but the main mutation risk is covered.

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?

Front-loaded with the action, then focused guidance on the one behavior that matters most. Four sentences, each carrying useful information with no repetition or filler.

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?

For an update tool with rich schema coverage but no annotations or output schema, the description covers the critical content-editing behavior and destructive default. It could mention partial updates via name/sub_title alone, but it is sufficient to call the tool correctly.

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 is 3. The description adds value beyond the schema by explaining the practical effect of content_edit_mode and newline handling for append/prepend, which helps an agent apply content correctly.

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?

States a specific verb and resource: 'Update a page in a ClickUp document.' This clearly distinguishes it from sibling tools like clickup_create_document_page or clickup_get_document_pages without needing the schema.

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?

Explains how to use content_edit_mode in context, including that append/prepend avoid a separate read and that replace is destructive. It does not explicitly name alternatives or when not to use this tool, but the operational guidance is clear.

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