Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_comment

Idempotent

Edit a comment's text, reassign it, or mark it resolved or unresolved to manage feedback and action items.

Instructions

Edit a comment's text, (re)assign it, or toggle its resolved state.

Calls PUT /comment/{comment_id}. Works uniformly on task, List, Chat-view, and threaded-reply comments — they all share the same comment_id space.

When to Use:

  • To fix a typo, add detail, reassign a comment's action item, or mark it resolved once addressed.

When NOT to Use:

  • To remove a comment entirely — use clickup_delete_comment.

  • To reply within a thread rather than editing — use clickup_create_threaded_comment.

Returns: A confirmation string naming the updated comment, or an Error ... string on failure.

Examples: params = {"comment_id": "446750", "comment_text": "Resolved — see PR #42.", "resolved": True}

Error Handling: 404 means the comment id is wrong; 403 can mean you don't own the comment and lack edit permission.

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?

Discloses REST API call (PUT /comment/{comment_id}), return type, and error codes (404, 403). Annotations provide readOnlyHint false and destructiveHint false; description adds API details and error handling.

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?

Well-organized: overview, API call, usage guidance, return, example, error handling. All sentences are informative and concise.

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?

Covers all necessary aspects: purpose, when/not to use, error handling, return value. An output schema exists, so return description is sufficient.

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?

Schema already has detailed descriptions for all parameters (e.g., 'comment_id', 'comment_text', 'resolved'). The description example shows usage but doesn't add significant new meaning beyond schema.

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 edits a comment's text, reassigns it, or toggles resolved state. It distinguishes from siblings like clickup_delete_comment and clickup_create_threaded_comment.

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 'When to Use' and 'When NOT to Use' sections with examples and alternatives (e.g., deletion or threaded replies).

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