Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_edit_page

Idempotent

Update a Doc page's title, subtitle, or content with replace, append, or prepend modes. Ideal for renaming pages or adding logs without overwriting.

Instructions

Update a Doc page's title, subtitle, and/or content.

content_edit_mode controls how content is applied: replace (default) overwrites the page body, append adds to the end, prepend adds to the start — handy for logging into an existing page without a read-modify-write.

When to Use:

  • To rename a page, change its subtitle, or overwrite/append/prepend content.

When NOT to Use:

  • To create a new page — use clickup_create_page.

Returns: A confirmation naming the page, Doc, and edit mode used.

Examples:

  • params = {"doc_id": "d", "page_id": "p", "content": "new body"}

  • params = {"doc_id": "d", "page_id": "p", "content": "- log", "content_edit_mode": "append"}

Error Handling: 404 → page not found. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Description adds value beyond annotations by explaining content_edit_mode (replace/append/prepend), return confirmation, and error handling. Annotations indicate idempotent and non-destructive; description aligns and adds context.

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?

Description is well-structured with clear sections (summary, edit mode, when, returns, examples, error handling). Slightly verbose but front-loaded with core action.

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?

Covers main parameters and behavior. With output schema present, return value explanation is adequate. Missing details on workspace_id and content_format, but overall sufficient for typical use.

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?

With schema description coverage at 0%, description partially compensates by explaining name, subtitle, content, and content_edit_mode. However, workspace_id and content_format are not mentioned in description, relying on schema which counts as no coverage.

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?

Description clearly states 'Update a Doc page's title, subtitle, and/or content' with specific verb and resource. Distinguishes from sibling clickup_create_page by stating when NOT to use this 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?

Explicitly provides 'When to Use' and 'When NOT to Use' sections, naming clickup_create_page as alternative. Also explains content_edit_mode behavior and gives examples.

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/trustxai/clickup-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server