Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_edit_user_on_workspace

Idempotent

Update a workspace member's username, admin privileges, or custom role. Note: only available on Enterprise plans.

Instructions

Update a Workspace member's username, admin flag, or custom role.

Only the fields you pass are sent. Note: Enterprise plan only — returns 403 on other plans.

When to Use:

  • Renaming a member, promoting/demoting admin access, or reassigning a custom role.

When NOT to Use:

  • Editing a guest's permission flags — use clickup_edit_guest_on_workspace instead.

Returns: A confirmation string listing the fields that were updated, or an Error ... string on failure.

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

Error Handling: 403 means the Workspace is not on the Enterprise plan (or you lack admin rights). 404 means the user id does not exist on this Workspace.

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?

Annotations already indicate a write operation (readOnlyHint=false) that is not destructive (destructiveHint=false) and idempotent (idempotentHint=true). The description adds valuable context: only passed fields are sent (partial update), Enterprise plan restriction, and error codes (403, 404) with meanings. 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-organized into sections (purpose, when to use, when not to use, returns, examples, error handling). Every sentence adds value, with no redundancy or fluff. It is concise yet comprehensive.

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 complexity (update on workspace with multiple editable fields), the description covers all necessary aspects: purpose, usage boundaries, return type (confirmation string or error), and error handling. The existence of an output schema (not shown) further complements the description.

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 already provides descriptions for each parameter (e.g., admin: 'Whether the member should have admin privileges'), so the description does not need to repeat them. However, the description adds the crucial behavioral detail that only passed fields are sent, which enhances understanding. The example also clarifies usage.

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 the action (update a workspace member's username, admin flag, or custom role) and specifies the resource (workspace member). It distinguishes itself from the sibling tool for editing guests, providing clear differentiation.

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?

The description explicitly lists when to use the tool (renaming, promoting/demoting admin, reassigning custom role) and when NOT to use it (altering guest permissions), with a direct reference to the alternative clickup_edit_guest_on_workspace. It also notes the Enterprise plan requirement.

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