Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_remove_custom_field_value

DestructiveIdempotent

Clear a custom field's value on a task using its field ID. Use when you need to empty a field without deleting the field definition.

Instructions

Clear a Custom Field's value on a task.

Calls DELETE /task/{task_id}/field/{field_id}. This removes the value stored on the task only — it does NOT delete the field definition or any drop_down/labels options from the field's configuration.

When to Use:

  • To empty a single field on a task (e.g. unset a drop_down or clear a date).

When NOT to Use:

  • To change a value — use clickup_set_custom_field_value.

  • To delete the field itself — that is a ClickApp/UI action, not this API.

Returns: A confirmation string (the endpoint returns an empty body on success).

Examples:

  • params = {"task_id": "9hz", "field_id": ""}

  • params = {"task_id": "ABC-123", "field_id": "", "custom_task_ids": true, "team_id": "9007200144"}

Error Handling: 404 means the task or field_id is wrong; if custom_task_ids=true you must also pass team_id.

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?

Annotations indicate destructiveHint: true, readOnlyHint: false. The description confirms it is a mutating operation and adds crucial context: it only removes the value, not the field definition. Error handling details further enhance transparency.

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-structured with clear sections (purpose, when to use/not use, return, examples, error handling). It is concise yet informative, with no wasted words.

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?

Given the tool has multiple parameters and an output schema, the description covers all necessary aspects: operation, usage boundaries, return value, and error scenarios. It is complete for an agent to correctly select and invoke the tool.

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?

The description adds meaning beyond the schema by providing concrete examples and clarifying the conditional requirement of team_id when custom_task_ids=true. The schema descriptions are already present, but the description's examples and error conditions add practical value.

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 action: 'Clear a Custom Field's value on a task.' It specifies the HTTP method and endpoint, and distinguishes from sibling tools like clickup_set_custom_field_value and the deletion of the field itself.

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 with direct references to sibling tools. Also provides error handling guidance for 404 errors and the custom_task_ids constraint.

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