Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_delete_user_group

DestructiveIdempotent

Permanently remove a stale or duplicate User Group from your ClickUp Workspace by providing its group ID. Member accounts remain unaffected.

Instructions

Permanently delete a User Group from a Workspace.

Calls DELETE /group/{group_id} (ClickUp's endpoint slug is deleteteam, but this deletes a User Group, not the Workspace itself — group_id is never a team_id). Deleting the group does not delete the member accounts; members keep whatever direct or inherited access they already had outside the group.

When to Use:

  • To remove a stale or duplicate User Group.

When NOT to Use:

  • To remove a single member while keeping the group, use clickup_update_user_group with remove_member_ids instead.

Returns: A confirmation string once the group is deleted.

Examples: params = {"group_id": "4bfdfcec-6f4f-40a7-b0d6-22660d51870d"}

Error Handling: 404 if group_id doesn't exist (it may already be deleted); 403 if the token lacks permission.

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 (destructiveHint=true, idempotentHint=true), the description adds context: the delete is permanent, does not delete member accounts or affect their access outside the group, and the API endpoint slug is misleading. 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: main purpose, when to use, when not to use, returns, example, error handling. Each sentence adds value, and the length is appropriate for the complexity.

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, the description adequately covers purpose, usage, behavior, parameter details, example, and errors. It provides sufficient context for an agent to correctly select and invoke this tool.

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 input schema already provides a clear description for group_id: 'User Group id to permanently delete. This is NOT a Workspace/team_id.' The description repeats this caution and adds context about the endpoint but does not add significant new parameter semantics. Baseline of 3 maintained as schema description coverage is high.

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 'Permanently delete a User Group from a Workspace.' It explains the API endpoint slug discrepancy and distinguishes from deleting the workspace or members. The verb 'delete' and resource 'User Group' are specific, and it notably differentiates from sibling tools like clickup_delete_space or clickup_delete_task.

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 are provided. The NOT to Use case specifies an alternative: 'clickup_update_user_group' for removing individual members. It also includes error handling notes for 404 and 403 responses.

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