Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_user_groups

Read-onlyIdempotent

List all User Groups in a ClickUp Workspace. Use this to retrieve group IDs for updating or deleting groups, or to audit group membership.

Instructions

List the User Groups in a Workspace (ClickUp's endpoint slug: "getteams1").

Calls GET /group?team_id=.... NB the naming trap: the underlying ClickUp endpoint is historically named "Teams", but the resource returned is a User Group (group_id), not the Workspace itself (team_id) — pass the Workspace id via team_id and optionally narrow to specific groups via group_ids.

When to Use:

  • To look up a group's group_id before calling clickup_update_user_group / clickup_delete_user_group.

  • To audit which User Groups exist in a Workspace and who is in them.

When NOT to Use:

  • To list plain (ungrouped) Workspace members, use a Workspace-members tool in another module — this tool only returns User Groups.

Returns: A markdown (or JSON) list of groups with group_id, name, handle, and member count.

Examples: params = {"team_id": "123456"} params = {"team_id": "123456", "group_ids": ["4bfdfcec-6f4f-40a7-b0d6-22660d51870d"]}

Error Handling: 400/404 if team_id is missing or 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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds implementation details (HTTP call), naming trap warning, and error handling (400/404), which provides useful behavioral context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with headings and examples, but it is fairly long. It front-loads the main action and includes necessary details. It is not overly verbose, but could be slightly more concise without losing clarity.

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 simplicity (1 required param, output schema exists) and annotations covering safety, the description is thorough: it covers purpose, usage guidelines, error handling, return format, and examples. It leaves no obvious gaps for an agent to make mistakes.

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

Parameters4/5

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

The input schema has full descriptions for all parameters (team_id, group_ids, response_format). The description adds semantic clarification: explains the team_id vs group_id distinction, provides examples, and describes the output format selector. This goes beyond the schema 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 clearly states 'List the User Groups in a Workspace' and specifies the endpoint slug. It distinguishes the tool from sibling tools by clarifying the naming trap and resource type, making it easy for an agent to understand exactly what this tool returns.

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?

Includes explicit 'When to Use' and 'When NOT to Use' sections. It tells the agent to use this for looking up group_id before update/delete, and to use a different tool for listing plain workspace members. This provides clear guidance on tool selection.

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