Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_space_custom_fields

Read-onlyIdempotent

List custom fields available at a Space scope, including inherited from workspace, to audit fields exposed to folders, lists, and tasks.

Instructions

List the Custom Fields available at a Space scope.

Calls GET /space/{space_id}/field, returning fields defined on the Space plus those inherited from the Workspace.

When to Use:

  • To audit which fields a Space exposes to its Folders, Lists, and tasks.

When NOT to Use:

  • To find a field usable on a specific task — use clickup_get_list_custom_fields.

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

Examples:

  • params = {"space_id": "790"}

Error Handling: 404 means the Space 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 declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds behavioral context: inheritance from Workspace, return format (markdown vs JSON), and error handling. This extra context justifies a score above baseline but not a 5 since annotations already do significant work.

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, behavior, usage, returns, example, errors). It is concise with no wasted words. Every sentence earns its place.

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

Completeness4/5

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

Given the output schema exists, the description explains what is returned and covers error scenarios. It differentiates from sibling tools adequately. A score of 4 reflects that while thorough, it could optionally mention pagination or limits, but it's sufficient for the tool's complexity.

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?

The input schema provides descriptions for all parameters (space_id, response_format, include_applied_objects). The description adds error codes related to parameters but does not significantly enhance understanding beyond what the schema provides. Baseline 3 is appropriate.

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 verb 'List' and the resource 'Custom Fields available at a Space scope.' It distinguishes from siblings by noting inheritance from Workspace and explicitly tells when not to use this tool, directing to clickup_get_list_custom_fields.

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?

There are explicit 'When to Use' and 'When NOT to Use' sections, providing clear context. It names an alternative tool (clickup_get_list_custom_fields) for a different use case, helping the agent decide correctly.

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