Skip to main content
Glama

clickup_group_delete

Permanently delete a ClickUp user group. Assignments and mentions remain as historical records, but the group is no longer usable.

Instructions

Permanently delete a ClickUp user group. Destructive and irreversible — assignments and mentions that referenced the group remain as historical records, but the group can no longer be used going forward. The individual users are not affected. Returns an empty object on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesID of the group to delete. Obtain from clickup_group_list (field: id).
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description fully discloses the destructive and irreversible nature, that historical records remain, and that individual users are unaffected. It also notes the return value (empty object). This is transparent for a deletion tool.

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 two sentences long with no wasted words: first sentence states the action, second explains consequences and return value. It is efficiently structured.

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 simplicity of the tool (one parameter, no output schema, no annotations), the description covers the purpose, behavioral details, and return value completely. No additional context is needed.

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 description for the sole required parameter 'group_id', including a source hint ('Obtain from clickup_group_list'). The description does not add further meaning beyond the schema, so a baseline score of 3 is appropriate.

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 ClickUp user group', using a specific verb and resource. It distinguishes itself from sibling tools like clickup_group_create, clickup_group_list, and clickup_group_update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on the consequences (destructive, irreversible, effects on references and users), but does not explicitly state when to use this tool versus alternatives like clickup_group_update for deactivation. It implies use when permanent deletion is intended.

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/nicholasbester/clickup-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server