Skip to main content
Glama

clickup_field_set

Set or overwrite a custom field value on a ClickUp task. Provide the field ID, task ID, and the new value matching the field type.

Instructions

Set or overwrite a single custom field value on a ClickUp task. The value's JSON shape must match the field type (string for text/url/email and for a drop_down option id, number for number/currency/progress, array of option ids for labels, Unix ms for date, etc.). Use clickup_field_list first to see the field type and option ids. Use clickup_field_unset to clear a value. Returns an empty object on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
field_idYesID of the custom field to set. Obtain from clickup_field_list (field: id) or clickup_task_get (custom_fields[].id).
task_idYesID of the task whose field value should change. Obtain from clickup_task_list (field: id).
valueYesNew value; the accepted type depends on the custom field type. Examples: 'hello' (text), 42 (number), 'option-uuid' (drop_down), ['option-uuid'] (labels), 1735689600000 (date as Unix ms). See clickup_field_list for the field's type and option ids.
Behavior4/5

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

Discloses that the value's JSON shape must match the field type and provides examples. Returns empty object on success. Lacks mention of error conditions or authentication, but overall adequately transparent for a mutation tool.

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?

Extremely concise: two sentences with no filler. Front-loads purpose, then provides essential type guidance and related tool references.

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?

For a simple field-set tool, the description covers the main points: purpose, value constraints, prerequisite tool, and success return. Could mention that the operation overwrites existing values, but that's implied. Still nearly 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?

Input schema has 100% coverage with descriptions for all three parameters. The tool's description reinforces the value type requirements but adds minimal new information beyond the schema's own examples and instructions.

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?

Description clearly states the tool sets or overwrites a custom field value on a ClickUp task. It distinguishes itself from siblings like clickup_field_list (to inspect) and clickup_field_unset (to clear).

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 instructs to use clickup_field_list first to determine field type and option ids, and points to clickup_field_unset for clearing values. This gives clear context for when and how to use the tool.

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/nicholasbester/clickup-cli'

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