Skip to main content
Glama

custom_fields_values

Read, set, remove, or bulk-update custom field values on ClickUp tasks, supporting dropdowns, dates, people, and location fields.

Instructions

Get, set, remove, or bulk-set custom field values on ClickUp tasks. Use "get" to read all field values on a task, "set" to write a value, "remove" to clear it, or "bulk_set" to set values across multiple tasks in one operation. For dropdown/labels fields, pass the option UUID (get UUIDs from custom_fields tool with action="list"). For date fields, pass a Unix timestamp in milliseconds. For people fields, pass {add:[user_ids], rem:[user_ids]}. For location fields, pass {lat:number, lng:number, formatted_address?:string}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueNoRequired for set: the value. Format depends on field type: text/url/email/phone → string number/rating → number checkbox → boolean date → Unix timestamp ms dropdown → option UUID labels → array of option UUIDs people → {add:[ids], rem:[ids]} location → {lat, lng, formatted_address}
actionYesAction to perform
task_idNoRequired for get, set, remove: the task ID
updatesYesArray of {task_id, field_id, value} objects (bulk_set only)
field_idNoRequired for set, remove: the custom field ID
continue_on_errorNoContinue if an individual update fails (bulk_set)
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description is the sole source of behavioral context. It discloses input formats for various field types, which is useful, but it does not mention potential side effects, error behavior, permission requirements, or idempotency. For a mutation-capable tool, this is a moderate transparency level.

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 a single compact paragraph that front-loads the core purpose and then methodically explains each action and field format. Every sentence adds value, and the structure is logical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the main operations and all field type formats, which is substantial for a tool with 6 parameters and multiple actions. Given the absence of an output schema, it does not describe return values, but that is not essential. It could have added a note about what 'get' returns, but overall it is sufficiently complete.

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?

The schema description coverage is 100%, and the description largely mirrors the schema's parameter details, especially for the 'value' parameter. It does add a cross-tool reference for UUIDs, but overall it does not significantly enhance understanding beyond the schema's own explanations.

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 explicitly lists the verbs 'get, set, remove, or bulk-set' and identifies the resource as 'custom field values on ClickUp tasks'. This clearly distinguishes it from sibling tools like 'custom_fields' which likely manage field definitions.

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 provides explicit guidance for each action: 'Use "get" to read all field values on a task, "set" to write a value, "remove" to clear it, or "bulk_set" to set values across multiple tasks'. It also directs users to the 'custom_fields' tool to obtain option UUIDs for dropdowns/labels, showing awareness of alternatives.

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/benthesoundguy/clickup-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server