Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_custom_roles

Read-onlyIdempotent

List custom roles configured in a ClickUp workspace, including their base role and optionally assigned members.

Instructions

List the Custom Roles configured for a Workspace.

Calls GET /team/{team_id}/customroles (team_id = Workspace id; this endpoint has no relation to User Groups/group_id). Custom Roles let a Workspace define named permission tiers layered on top of ClickUp's base roles (owner/admin/member/guest); each role's inherited_role shows which base role it extends.

Note: Custom Roles are an Enterprise plan feature — this endpoint returns 403 on other plans.

When to Use:

  • To look up which Custom Role(s) exist, and who holds them, before assigning one to a user elsewhere.

When NOT to Use:

  • To list User Groups (an unrelated, non-permission concept), use clickup_get_user_groups.

Returns: A markdown (or JSON) list of roles with id, name, the base role they extend, and (when include_members=True) member count.

Examples: params = {"team_id": "123456"} params = {"team_id": "123456", "include_members": false}

Error Handling: 403 on non-Enterprise plans; 404 if team_id is invalid.

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?

Adds details beyond annotations: Enterprise plan requirement, 403 error, explanation of inherited_role, response content, and error handling. Annotations already indicate safe read/ idempotent nature.

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?

Well-structured with headings and examples, but slightly lengthy. Front-loaded with main purpose. No redundant sentences.

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 low complexity, presence of output schema, and good annotations, the description provides sufficient context including error handling and usage examples.

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 signal, description thoroughly explains team_id (not group_id), include_members, and response_format, adding clarity beyond 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?

Clearly states 'List the Custom Roles configured for a Workspace', specifies the API endpoint, and distinguishes from sibling tool clickup_get_user_groups for User Groups.

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, naming the alternative tool and noting Enterprise plan restriction.

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