Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_user_group

Idempotent

Update a user group's name, handle, or membership by specifying group ID and changes to add or remove members.

Instructions

Rename a User Group and/or add/remove its members.

Calls PUT /group/{group_id} (ClickUp's endpoint slug is updateteam, but group_id here addresses a User Group, never a Workspace — do not pass a team_id in this field). Member changes use ClickUp's {"add": [...], "rem": [...]} shape nested under members; name and handle are replaced wholesale when provided.

When to Use:

  • To rename a group, change its @mention handle, or add/remove members without deleting and recreating the group.

When NOT to Use:

  • To create a brand-new group, use clickup_create_user_group.

  • To remove the group entirely, use clickup_delete_user_group.

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

Examples: params = {"group_id": "4bfdfcec-6f4f-40a7-b0d6-22660d51870d", "name": "QA Team"} params = { "group_id": "4bfdfcec-6f4f-40a7-b0d6-22660d51870d", "add_member_ids": [123456], "remove_member_ids": [159753], }

Error Handling: 404 if group_id doesn't exist; 403 if the token lacks permission. 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?

Beyond annotations (readOnlyHint false, destructiveHint false, idempotentHint true), the description discloses endpoint details, member update shape, error codes (404, 403), and a billing warning for adding view-only guests. This adds significant behavioral context.

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 sections (purpose, when to use, when not to use, returns, examples, error handling). Every sentence adds value; no filler. It is front-loaded with the core action.

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 tool's complexity (rename, handle, add/remove members, error handling, billing impact), the description covers all essential aspects. It references sibling tools and provides an output description. Nothing is missing.

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?

Despite 0% schema description coverage for the top-level parameter, the description explains the meaning of group_id (not a team_id), clarifies how add_member_ids and remove_member_ids work via examples, and provides usage context beyond the schema's property 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?

The description explicitly states 'Rename a User Group and/or add/remove its members', providing a specific verb and resource. It differentiates from sibling tools like clickup_create_user_group and clickup_delete_user_group by outlining when to use and when not to use.

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 clear 'When to Use' and 'When NOT to Use' sections, explicitly naming alternatives (clickup_create_user_group, clickup_delete_user_group) and providing context for when this tool should be chosen.

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