Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_list_custom_fields

Read-onlyIdempotent

Discover all custom fields available on a List, including inherited ones, and retrieve their IDs and option UUIDs to use when setting field values on tasks.

Instructions

List the Custom Fields accessible from a List.

Calls GET /list/{list_id}/field. This is the scope you almost always want before setting a value: it returns every field usable on the List's tasks — fields defined on the List plus those inherited from the parent Folder, Space, and Workspace. Each field object carries the id (a UUID you pass to clickup_set_custom_field_value), type, and type_config (for drop_down / labels fields, type_config.options[] holds the option UUIDs you set).

When to Use:

  • To discover a field's id and its option UUIDs before calling clickup_set_custom_field_value on a task in this List.

When NOT to Use:

  • For fields defined higher up only: prefer the narrowest scope that includes your task. Use clickup_get_folder_custom_fields, clickup_get_space_custom_fields, or clickup_get_team_custom_fields to inspect a specific level.

Returns: A markdown list of fields (name, type, id, and any options) or, with response_format="json", the raw field objects including full type_config.

Examples:

  • params = {"list_id": "901100154842"}

  • params = {"list_id": "901100154842", "include_applied_objects": true, "response_format": "json"}

Error Handling: 404 means the List id is wrong; 401/403 point to token or access issues.

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?

Adds detail beyond annotations: explains inherited field scoping, response structure (id, type, type_config), and error handling (404, 401/403).

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?

Well-structured with sections for purpose, when to use/not use, returns, examples, and error handling; every sentence adds value without fluff.

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?

Complete given low complexity: covers scope, input, output, examples, errors, and sibling tools. Output schema exists, so return details are sufficient.

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?

Despite 0% schema coverage, description explains each parameter's purpose (e.g., response_format markdown vs json) and provides usage examples, compensating for missing schema descriptions.

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 explicitly states it lists custom fields from a list, distinguishes from sibling tools like get_folder_custom_fields, get_space_custom_fields, and get_team_custom_fields by scoping.

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?

Clearly states when to use (before setting a value, to get field ID/options) and when not to use (for higher-level fields), naming alternative tools.

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