Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

clickup_set_custom_field_value

Update custom field values on ClickUp tasks to track project details, status updates, or specific attributes within your workspace.

Instructions

Set a value for a custom field on a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesClickUp task ID
custom_field_idYesCustom field ID
valueYesValue to set for the custom field. Type depends on the custom field type.

Implementation Reference

  • The MCP tool handler function that destructures input and calls the CustomFieldService to set the custom field value on a task, then returns the response as JSON text.
    handler: async (input) => {
      const { task_id, custom_field_id, value } = input;
      const response = await customFieldService.setCustomFieldValue(
        task_id,
        custom_field_id,
        value
      );
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    },
  • Zod input schema validating task_id, custom_field_id, and flexible value (string, number, boolean, array, or object).
    inputSchema: {
      task_id: z.string().describe("ClickUp task ID"),
      custom_field_id: z.string().describe("Custom field ID"),
      value: z
        .union([
          z.string(),
          z.number(),
          z.boolean(),
          z.array(z.unknown()),
          z.record(z.unknown()),
        ])
        .describe(
          "Value to set for the custom field. Type depends on the custom field type."
        ),
    },
  • src/index.ts:89-91 (registration)
    Registers the clickup_set_custom_field_value tool (along with others) to the MCP server by calling server.tool() in a loop over the tools array.
    tools.forEach((tool) => {
      server.tool(tool.name, tool.description, tool.inputSchema, tool.handler);
    });
  • Service method that sends a POST request to ClickUp API to set the custom field value on the specified task.
    async setCustomFieldValue(
      taskId: string,
      customFieldId: string,
      value: any
    ): Promise<{ field: ClickUpCustomField }> {
      return this.request<{ field: ClickUpCustomField }>(
        `/task/${taskId}/field/${customFieldId}`,
        {
          method: "POST",
          body: JSON.stringify({ value }),
        }
      );
    }
  • src/index.ts:48-49 (registration)
    Includes the setCustomFieldValueTool in the tools array used for MCP server registration.
    getListCustomFieldsTool,
    setCustomFieldValueTool,
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Set a value' implies a write/mutation operation, it doesn't specify permissions required, whether the operation is idempotent, error handling for invalid field types, or what happens on success (e.g., no output schema is provided). For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and target, making it easy to parse. Every word earns its place by conveying essential information without redundancy.

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

Completeness3/5

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

Given the tool's complexity (a mutation operation with 3 parameters) and the absence of both annotations and an output schema, the description is minimally adequate. It states what the tool does but lacks behavioral details, usage context, and output information. For a mutation tool, this leaves significant gaps that could hinder correct agent invocation.

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 description coverage is 100%, with clear descriptions for all three parameters (task_id, custom_field_id, value). The description adds no additional parameter semantics beyond what's in the schema, such as explaining how to obtain the custom_field_id or format the value for specific field types. With high schema coverage, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Set a value') and the target ('for a custom field on a task'), which is specific and unambiguous. It distinguishes this tool from siblings like clickup_update_task (which modifies core task properties) and clickup_get_task (which retrieves data), though it doesn't explicitly mention the sibling clickup_set_custom_field_value_by_custom_id as an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tool clickup_set_custom_field_value_by_custom_id (which likely uses a custom task ID instead of the internal task_id), nor does it explain prerequisites like needing the custom field ID from clickup_get_list_custom_fields. Usage context is implied but not stated.

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

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