Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

clickup_set_custom_field_value_by_custom_id

Update custom field values on ClickUp tasks using their custom IDs to maintain accurate task data and workflow automation.

Instructions

Set a value for a custom field on a task using the task's custom ID

Input Schema

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

Implementation Reference

  • The handler function that executes the core logic of the MCP tool by calling the service method with destructured input parameters and formatting the response.
    handler: async (input) => {
      const { custom_id, custom_field_id, value } = input;
      const response = await customFieldService.setCustomFieldValueByCustomId(
        custom_id,
        custom_field_id,
        value
      );
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    },
  • Zod-based input schema defining the parameters: custom_id (string), custom_field_id (string), and value (union of common types).
    inputSchema: {
      custom_id: z.string().describe("ClickUp custom 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:23-50 (registration)
    Imports the tool from the controller and includes it in the array of tools that are registered to the MCP server.
      getListCustomFieldsTool,
      setCustomFieldValueTool,
      setCustomFieldValueByCustomIdTool,
    } from "./controllers/custom-field.controller";
    import { getListAssigneesTool } from "./controllers/assignee.controller";
    
    const tools = [
      // Task tools
      getTaskByCustomIdTool,
      getTaskTool,
      createTaskTool,
      updateTaskTool,
      updateTaskByCustomIdTool,
    
      // Space tools
      getSpacesTool,
    
      // Folder tools
      getFoldersTool,
    
      // List tools
      getListsTool,
      createListTool,
    
      // Custom Field tools
      getListCustomFieldsTool,
      setCustomFieldValueTool,
      setCustomFieldValueByCustomIdTool,
  • Helper service method that makes the POST request to the ClickUp API endpoint to set the custom field value using the task's custom ID.
    async setCustomFieldValueByCustomId(
      customId: string,
      customFieldId: string,
      value: any
    ): Promise<{ field: ClickUpCustomField }> {
      return this.request<{ field: ClickUpCustomField }>(
        `/task/${customId}/field/${customFieldId}?custom_task_ids=true&team_id=${this.workspaceId}`,
        {
          method: "POST",
          body: JSON.stringify({ value }),
        }
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the write operation ('Set a value') but doesn't mention permission requirements, whether the operation is idempotent, potential side effects, error conditions, or response format. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that communicates the core functionality without unnecessary words. It's appropriately sized for this tool's scope and front-loads the essential information. Every word earns its place.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address important contextual aspects like authentication requirements, error handling, what happens on success/failure, or how the value parameter interacts with different custom field types. The 100% schema coverage helps with parameters but doesn't compensate for missing behavioral context.

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%, providing good documentation for all three parameters. The description adds minimal value beyond the schema - it mentions 'custom field on a task' and 'custom ID' which are already covered in parameter descriptions. No additional semantic context about parameter relationships or usage patterns is provided.

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 target resource ('custom field on a task'), specifying the identifier method ('using the task's custom ID'). It distinguishes from the sibling 'clickup_set_custom_field_value' by explicitly mentioning the custom ID approach, though it doesn't fully explain the difference between these two similar tools.

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?

No explicit guidance on when to use this tool versus alternatives is provided. While it implies usage for tasks with custom IDs, it doesn't clarify when to choose this over 'clickup_set_custom_field_value' (which likely uses a different identifier) or other task-update tools like 'clickup_update_task_by_custom_id'. The description offers minimal contextual direction.

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