Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_privacy_and_access

Idempotent

Control object privacy and manage user/group access permissions for ClickUp items. Grant or revoke read, comment, edit, create, or remove access on tasks, lists, docs, and more.

Instructions

Set the privacy of an object and grant/revoke user or group access (Enterprise).

Flips an object private/public and/or edits its ACL. Each entries item sets a permission level for a user or group: 1=read, 3=comment, 4=edit, 5=create, or null to remove that principal's access. Works across ClickUp object types (task, list, folder, space, doc, dashboard, view, goal, …) via the object_type/object_id pair.

Note: Enterprise plan only — returns 403 on other plans. Sharing an item may incur seat/billing charges.

When to Use:

  • To make a List private and grant a group edit access.

  • To revoke a user's access to a Doc (permission_level: null).

When NOT to Use:

  • To invite someone to the whole Workspace — use the guests/users tools.

Returns: A confirmation of the privacy change and each access entry applied.

Examples:

  • params = {"object_type": "list", "object_id": "901300", "private": true, "entries": [{"kind": "group", "id": "88", "permission_level": 4}]}

  • params = {"object_type": "doc", "object_id": "8cb", "entries": [{"kind": "user", "id": "182", "permission_level": null}]}

Error Handling: 403 → not Enterprise or insufficient rights; 404 → unknown object. Errors return an Error ... string.

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?

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description discloses Enterprise-only restriction (403), billing implications, permission level mapping (1=read, 3=comment, etc.), and error handling (403/404). This adds significant behavioral context.

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 (main, when to use, when not, returns, examples, error handling), front-loads core purpose, and every sentence adds value without redundancy.

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?

For a complex tool with nested ACL entries and privacy toggle, the description covers plan restrictions, billing, error codes, supported object types, and provides examples. Output schema exists, so return values are not needed. The description is comprehensive for agent decision-making.

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?

With 0% schema description coverage (by context signals), the description explains the entries structure, permission level mapping, and null usage for removal. It provides two examples illustrating parameter combinations. However, workspace_id default behavior is not mentioned, and schema already has descriptions for some fields.

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 tool sets privacy and grants/revokes access, with specific verb 'Set' and resource 'privacy of an object and grant/revoke user or group access'. It lists supported object types, distinguishing from sibling tools like workspace invitation tools via the 'When NOT to Use' section.

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?

Explicit 'When to Use' and 'When NOT to Use' sections provide concrete examples (e.g., making a List private, revoking access) and direct the agent to alternative tools (guests/users tools) for workspace invitations, making usage boundaries very clear.

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