Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_user

Read-onlyIdempotent

Retrieve a ClickUp workspace member's profile, role, and admin status. Requires Enterprise plan.

Instructions

Look up a single Workspace member's profile, role, and admin status.

Note: Enterprise plan only — returns 403 on other plans.

When to Use:

  • Checking a member's current role/admin flag before editing or removing them.

When NOT to Use:

  • Listing every member of a List/Task — use clickup_get_list_members / clickup_get_task_members instead. Looking up a guest — use clickup_get_guest.

Returns: Markdown summary (id, username, email, role, custom role) or the raw JSON payload when response_format="json".

Examples: params = {"team_id": "123", "user_id": "456"}

Error Handling: 403 means the Workspace is not on the Enterprise plan. 404 means the user id does not exist on this Workspace.

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 declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds value by noting Enterprise plan restriction (403 on other plans), error handling for 403 and 404, and return format details.

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 clear sections (note, when to use, returns, examples, error handling). Concise but could be slightly shortened without losing information.

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?

Comprehensive for a read-only lookup tool with 4 parameters and output schema (described returns). Covers plan restrictions, error handling, and usage guidance.

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?

Schema covers all parameters with descriptions, so baseline is 3. Description does not add much beyond schema, except mentioning the params example. No contradiction.

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 the tool looks up a single Workspace member's profile, role, and admin status. Distinct from sibling tools like clickup_get_list_members and clickup_get_guest.

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?

Explicitly provides 'When to Use' and 'When NOT to Use' sections, including specific alternatives (clickup_get_list_members, clickup_get_task_members, clickup_get_guest).

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