Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_user_group

Create a user group in a workspace to organize members into reusable named sets for mentions and task assignments.

Instructions

Create a User Group (ClickUp's endpoint calls this a "Team") in a Workspace.

Calls POST /team/{team_id}/group. Despite the path living under /team/..., team_id here is the Workspace id — the resource created is a User Group, addressed afterwards by its own group_id (a UUID, e.g. "4bfdfcec-6f4f-40a7-b0d6-22660d51870d"). Never confuse the two: team_id = Workspace, group_id = User Group.

When to Use:

  • To create a reusable named set of members (e.g. "QA", "Product") that can be @mentioned or assigned as a unit across Spaces/Folders/Lists.

When NOT to Use:

  • To add/remove members on an existing group, use clickup_update_user_group instead of deleting and recreating it.

Returns: A confirmation string with the new group's group_id, name, and member count.

Examples: params = {"team_id": "123456", "name": "Product Managers", "members": [183, 812]}

Error Handling: 403 if the plan doesn't support User Groups or the token lacks permission; 400 if members contains invalid user ids. Note: adding a view-only guest to a group can convert them to a paid guest (billing impact) — ClickUp's own docs warn about this.

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 indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds value by explaining the API call details, return value, and warning about billing implications for adding view-only guests. No contradiction with annotations.

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: API explanation, usage guidelines, return value, examples, error handling. It is detailed but not verbose, and front-loads essential information.

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 complexity of the tool (parameter naming confusion, billing implications) and the presence of siblings, the description covers all necessary aspects: purpose, usage, parameters, behavior, errors, and examples. Complete for effective tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is 0%, the description compensates by explaining the meaning of each parameter (team_id is workspace id, members are user ids, handle for @mentions, etc.) and provides an example. It adds clarity beyond the input 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 it creates a User Group (called a Team in ClickUp's endpoint), specifies the HTTP method and path, and clarifies the confusing terminology (team_id vs group_id). It distinguishes from siblings like clickup_update_user_group and clickup_delete_user_group.

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?

The description includes explicit 'When to Use' and 'When NOT to Use' sections, providing clear guidance on when to use this tool vs alternatives (e.g., use clickup_update_user_group for adding/removing members). It also mentions error handling and billing impact.

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