Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_goal

Idempotent

Update a ClickUp Goal's name, due date, description, owners, or color. Add or remove owners incrementally; receive updated goal fields.

Instructions

Update an existing Goal's name, due date, description, owners, or color.

Owners are changed incrementally via add_owners/rem_owners rather than a full replacement list.

When to Use:

  • Renaming a Goal, pushing its due date, or changing who owns it.

When NOT to Use:

  • Editing a Key Result's progress — use clickup_edit_key_result.

Returns: A confirmation string with the Goal's fields after the update.

Examples: params = {"goal_id": "e53a033c-1146-4b58-b498-7ec39b5661c2", "add_owners": [123]}

Error Handling: 404 means the goal_id does not exist; 400 means a field value was rejected (e.g. malformed color or due_date).

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?

Annotations already indicate readOnlyHint=false, idempotentHint=true, destructiveHint=false. Description adds incremental owner behavior, return value (confirmation string), and error handling (404, 400). Could mention auth needs or side effects, but sufficient.

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-structured: purpose, incremental note, usage guidance, returns, example, error handling. Every section is concise and useful.

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 for a medium-complexity update tool: when to use, alternatives, parameter behavior, return value, error codes. Output schema exists to further detail return values.

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?

Input schema already provides descriptions for each parameter. Description adds value by explaining that owners are changed incrementally via add_owners/rem_owners, which is not fully captured in schema descriptions.

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?

Clearly states it updates an existing Goal's fields (name, due date, description, owners, color). Differentiates from clickup_edit_key_result in the 'When NOT to Use' section.

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 a direct sibling alternative (clickup_edit_key_result). Also notes incremental owner semantics.

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