Skip to main content
Glama

set_custom_field

Idempotent

Set or clear one of 15 custom field slots on a Kanban Tool task. Pair with list_custom_field_definitions to ensure value matches the field type.

Instructions

Set or clear one of the 15 custom_field_* slots on a task.

slot selects which numbered slot to write (1..15 inclusive — the Kanban Tool API exposes exactly 15). Pair with list_custom_field_definitions(board_id) to learn each slot's label and type on a given board before writing.

value is sent verbatim — strings, numbers, and booleans all work. Pass value=None to clear the slot: the wire body explicitly sends null (not omits the key), and a subsequent get_task will see custom_field_N: null. This differs from update_task semantics where None means omit; for custom fields None means clear.

Common 422 (KanbanToolValidationError with parsed field_errors): type mismatch — e.g. writing "hi" into a numeric slot, or a value not in options for a dropdown-typed slot. Inspect the slot's type/options via list_custom_field_definitions(board_id) before writing if the slot purpose is uncertain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
slotYes
valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
descriptionNo
board_idNo
workflow_stage_idNo
swimlane_idNo
positionNo
priorityNo
colorNo
due_dateNo
start_dateNo
tagsNo
assigned_user_idNo
archived_atNo
block_reasonNo
subtasks_countNo
subtasksNo
comments_countNo
timers_totalNo
time_trackersNo
created_atNo
updated_atNo
size_estimateNo
size_estimate_descriptionNo
time_estimateNo
search_tagsNo
card_colorNo
card_color_in_rgbNo
card_color_invertNo
card_type_idNo
recurring_scheduleNo
reminders_scheduleNo
linked_tasksNo
linked_tasks_statusNo
task_dependenciesNo
collaboratorsNo
attachmentsNo
attachments_countNo
created_by_idNo
moved_atNo
postponed_untilNo
subtasks_completed_countNo
external_idNo
external_linkNo
custom_fieldsNo
is_archivedYesTrue iff the task has an archival timestamp.
is_blockedYesTrue iff the task has a non-empty block reason.
Behavior5/5

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

The description goes beyond the annotations (which indicate idempotentHint true) by detailing the exact wire behavior: value=None sends null explicitly (not omission), which differs from update_task. It also describes the error condition for type mismatches, providing valuable behavioral insights.

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 concise and well-structured, with each sentence adding value. It is front-loaded with the core action and uses clear, direct language without unnecessary verbosity.

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's complexity (3 parameters, output schema exists, annotations present), the description is comprehensive. It explains slot numbering, value handling, error conditions, and integration with sibling tools. The output schema exists but is not discussed, which is acceptable per the evaluation rules.

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 to the slot parameter (numbered 1..15 inclusive) and the value parameter (any type, sent verbatim, None to clear). The task_id parameter is implied from the context but not explicitly described. Since schema coverage is 0%, this description compensates effectively for most parameters.

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 'Set or clear one of the 15 custom_field_* slots on a task', specifying the exact resource and operation. It distinguishes itself from the sibling tool 'update_task' by explicitly noting the difference in handling None values, making the purpose unambiguous.

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 on when to use the tool, including pairing with 'list_custom_field_definitions' to learn slot labels/types, and when to pass value=None to clear a slot. It also warns about common 422 errors and suggests inspecting slot type/options, offering clear context for correct usage.

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/VeryLongOrgNameSuchWow/kanbantool-mcp'

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