Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_entity_attachment

Upload a local file to a ClickUp task or File-type Custom Field. This is the modern method that replaces older attachment tools and is required for uploading to custom fields.

Instructions

Upload a local file to a task or File-type Custom Field (v3).

Reads the file at file_path and posts it as multipart/form-data to POST /v3/workspaces/{workspace_id}/{entity_type}/{entity_id}/attachments. After uploading to a Custom Field (entity_type='custom_fields'), call clickup_set_custom_field_value to associate the uploaded file with a task.

When to Use:

  • The modern replacement for clickup_create_task_attachment, and the only way to upload to a File-type Custom Field.

When NOT to Use:

  • To read existing attachments — use clickup_get_entity_attachments.

Returns: A confirmation with the new attachment's id and URL (never the file bytes).

Examples:

  • task: params = {"workspace_id": "123", "entity_type": "attachments", "entity_id": "abc", "file_path": "/tmp/a.png"}

  • custom field: params = {"workspace_id": "123", "entity_type": "custom_fields", "entity_id": "fld-1", "file_path": "./a.png"}

Error Handling: A ValidationError before the request means the path is missing/empty/too large; a 404 means the entity_id was not found — or the v3 attachments surface is not available on this Workspace (verified live: some plans 404 on this endpoint entirely; use clickup_create_task_attachment for task files in that case).

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 indicate readOnlyHint=false and destructiveHint=false, consistent with the write operation. The description adds context: it posts multipart/form-data, returns id and URL (never bytes), and notes that some plans may 404. It does not explicitly mention file size limits or cleanup behavior, but overall adds good transparency beyond 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?

The description is well-organized with sections for purpose, mechanism, usage guidance, return value, examples, and error handling. Every sentence adds value without 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 tool's complexity (binary entity_type, dependency on another tool, error cases), the description covers all necessary aspects: the upload process, required follow-up for custom fields, return values, and error scenarios. It is complete for an agent to use correctly.

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 input schema already describes each parameter, but the description adds crucial context: the distinction between entity_type 'attachments' vs 'custom_fields', that file_path must be local, and the post-upload step for custom fields using `clickup_set_custom_field_value`. Examples further clarify usage, compensating for any 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 uploads a local file to a task or File-type Custom Field (v3). It distinguishes itself from siblings like `clickup_create_task_attachment` (modern replacement) and `clickup_get_entity_attachments` (for reading), 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?

Explicit 'When to Use' and 'When NOT to Use' sections name alternatives and provide fallback guidance. Error handling explains when to use `clickup_create_task_attachment` if the endpoint returns 404, leaving no ambiguity.

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