Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_entity_attachments

Read-onlyIdempotent

Retrieve attachments from a task or File-type Custom Field in ClickUp. Paginated with cursor support.

Instructions

List the attachments of a task or File-type Custom Field (v3).

Calls GET /v3/workspaces/{workspace_id}/{entity_type}/{entity_id}/attachments and returns the page of attachments plus the cursor for the next page.

When to Use:

  • To enumerate the files attached to a task (entity_type='attachments') or a File Custom Field (entity_type='custom_fields').

When NOT to Use:

  • To upload a file — use clickup_create_entity_attachment or clickup_create_task_attachment.

Returns: Each attachment's title, id, size, and URL. When more results exist, the response includes the cursor to pass back as cursor for the next page.

Pagination: Cursor-based and asymmetric — the request takes cursor, the response returns next_cursor. Loop: pass the returned next_cursor back as cursor until it is absent.

Examples:

  • task: params = {"workspace_id": "123", "entity_type": "attachments", "entity_id": "abc"}

  • custom field: params = {"workspace_id": "123", "entity_type": "custom_fields", "entity_id": "fld-1", "limit": 20}

Error Handling: A 404 means the entity_id was not found — or the v3 attachments surface is not available on this Workspace at all (verified live on a Business-plan workspace: even reads 404). If both tools here 404 on ids that definitely exist, fall back to clickup_create_task_attachment (v2) for task files. A 400 usually means entity_type and entity_id do not match (e.g. a Custom Field ID with entity_type='attachments').

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?

Beyond annotations (readOnly, idempotent), the description details cursor-based pagination, loop pattern, and specific error handling (404 meanings, 400 mismatches), providing rich behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections (purpose, when to use/not use, pagination, examples, error handling). Slightly verbose but efficient for the complexity; could be tightened but still strong.

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, zero schema coverage, and presence of output schema, the description covers return values, pagination, errors, and usage context comprehensively. No gaps identified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the input schema has 0% description coverage, the description elaborates on each parameter (entity_type options, cursor, limit, etc.) with examples and clarifies entity_id meaning, fully compensating for schema gaps.

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 tool lists attachments of a task or File-type Custom Field. It specifies the API endpoint and distinguishes from sibling upload tools, 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?

Includes explicit 'When to Use' and 'When NOT to Use' sections, directing to use for enumerating attachments and advising against using for uploads, with alternatives provided. Also covers fallback on 404 errors.

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