Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_folder_custom_fields

Read-onlyIdempotent

Retrieve custom fields available at a Folder scope, including those inherited from parent Space and Workspace. Use to audit accessible fields for Lists and tasks.

Instructions

List the Custom Fields available at a Folder scope.

Calls GET /folder/{folder_id}/field, returning fields defined on the Folder plus those inherited from the parent Space and Workspace.

When to Use:

  • To audit which fields a Folder exposes to its Lists and tasks.

When NOT to Use:

  • To find a field usable on a specific task — use clickup_get_list_custom_fields for the narrowest, task-applicable set.

Returns: A markdown list of fields (or raw JSON with response_format="json").

Examples:

  • params = {"folder_id": "457"}

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already convey read-only, idempotent, non-destructive behavior. Description adds the API endpoint, inheritance behavior, output format options, and specific error responses (404, 401/403). No contradictions with annotations.

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?

Description is concise and well-structured: purpose, details, usage guidelines, return format, example, error handling. Every sentence adds value with no redundancy.

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 presence of annotations and an output schema, the description provides sufficient behavioral context, usage differentiation, and error handling. The tool is fully understandable for correct selection and 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?

Description includes an example and mentions the response_format usage, but input schema already describes all parameters with detailed descriptions. The additional value is marginal; schema covers semantics well.

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?

Clearly states it lists Custom Fields at Folder scope, includes inherited fields, and explicitly differentiates from sibling tool clickup_get_list_custom_fields. The verb 'List' and resource 'Folder Custom Fields' with scope details provide high specificity.

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?

Provides explicit 'When to Use' and 'When NOT to Use' sections, advising to use an alternative for task-specific fields. Also includes error handling guidance for common HTTP status codes.

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