Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_goal

Create a new goal to group key results and track progress toward a target date in your ClickUp workspace.

Instructions

Create a new Goal in a Workspace.

Goals group one or more Key Results (see clickup_create_key_result) that track progress toward a target date.

When to Use:

  • Starting a new OKR / objective that will hold Key Results.

When NOT to Use:

  • To add a Key Result to an existing Goal — use clickup_create_key_result.

  • To change an existing Goal's fields — use clickup_update_goal.

Returns: A confirmation string with the new Goal's id and current fields.

Examples: params = {"name": "Grow MRR", "due_date": 1735689600000, "color": "#32a852"}

Error Handling: 404 usually means the team_id is wrong; 401 means the token is missing/invalid.

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 a non-read-only, non-destructive operation. The description adds context on grouping key results, return value, and error scenarios, but does not elaborate on open-world implications or rate limits.

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 and concise: purpose, relationship to other tools, usage guidance, return type, example, and error handling, all in a few sentences.

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 presence of an output schema and rich annotations, the description covers all necessary context: action, usage, alternatives, errors, and an example, making it fully complete.

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?

The schema already provides descriptions for all parameters, and the function description adds an example but no additional semantic meaning beyond what the schema offers.

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 verb 'Create' and the resource 'Goal' in a Workspace, and distinguishes from related tools like clickup_create_key_result and clickup_update_goal.

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, including specific alternative tool names and error handling codes, providing clear guidance.

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