Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_chat_message

Idempotent

Update a chat message's content, assignee, or resolved state. Send only the fields you want to change.

Instructions

Edit a Chat message's content, assignee, or resolved state.

Send only the fields you want to change; resolved is a top-level body field (not part of post_data).

When to Use:

  • To fix a message's text, (re)assign it, or mark a post resolved/unresolved.

When NOT to Use:

  • To remove a message entirely — use clickup_delete_chat_message.

  • To react to it — use clickup_add_chat_reaction.

Returns: A confirmation naming the message and the fields changed.

Examples:

  • params = {"message_id": "abc123", "content": "edited text"}

  • params = {"message_id": "abc123", "resolved": true}

Error Handling: 404 → unknown message id. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already provide readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds that it returns a confirmation, handles 404 errors, and that 'resolved' is a top-level body field, complementing annotations without contradiction.

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?

The description is well-structured with clear sections, bullet points for use cases, examples, and error handling. Every sentence is informative and earns its place.

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 input schema covers parameters, output schema exists (confirmation), and annotations present, the description is comprehensive: it covers purpose, usage guidelines, examples, and error handling. No gaps.

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?

Input schema properties already have descriptions (e.g., 'New message body (omit to leave unchanged)'). The description adds little beyond summarizing that only changed fields need to be sent and noting the special handling of 'resolved', but this is minimal added value.

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 it edits a Chat message, specifying editable fields (content, assignee, resolved state). It contrasts with sibling tools like delete and react, making the purpose unambiguous.

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 provide clear guidance, naming specific sibling tools (clickup_delete_chat_message, clickup_add_chat_reaction) for alternatives.

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