Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_task_attachment

Upload a local file from your filesystem to a ClickUp task as an attachment. Supports custom task IDs when a team ID is provided.

Instructions

Upload a local file to a task as an attachment (v2).

Reads the file at file_path from the local filesystem and posts it to the task as multipart/form-data (the ClickUp file field is attachment). Files already stored in the cloud cannot be used here.

When to Use:

  • To attach a document, image, or log file that exists on the local disk to a task.

When NOT to Use:

  • To upload to a File-type Custom Field, or if you prefer the newer API — use clickup_create_entity_attachment (v3).

  • To read existing attachments — use clickup_get_entity_attachments.

Returns: A confirmation with the new attachment's id and URL. The file bytes are never echoed back.

Examples:

  • params = {"task_id": "abc", "file_path": "/tmp/report.pdf"}

  • custom task ID: params = {"task_id": "PROJ-1", "file_path": "./log.txt", "custom_task_ids": true, "team_id": "123"}

Error Handling: A ValidationError before the request means the path is missing/empty/too large; a 404 means the task ID is wrong.

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?

Describes behavior: reads local file, posts as multipart/form-data, file not echoed back. Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, consistent with mutation. No contradiction. Adds error handling details (ValidationError for path issues, 404 for wrong task ID).

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 sections (purpose, when to use, returns, examples, error handling). Front-loaded with core purpose. Slightly long but each section earns its place for a complex tool. Could be trimmed slightly but still effective.

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?

Covers all necessary aspects: purpose, usage scope, alternatives, parameter behavior, return value, examples, error handling. No gaps given the tool's complexity and the presence of output schema (return values not needing further explanation).

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?

Description adds meaning beyond schema descriptions: explains file_path must be local, filename defaults to basename, custom_task_ids usage with team_id. Examples demonstrate parameter combinations. Enhances understanding of how parameters interact.

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 clearly states 'Upload a local file to a task as an attachment (v2)'. It specifies the verb (upload), resource (local file to task), and version. Distinguishes from sibling tools like clickup_create_entity_attachment and clickup_get_entity_attachments.

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. Lists alternatives: use clickup_create_entity_attachment for v3 or file-type custom fields, use clickup_get_entity_attachments for reading. Clear guidance on prerequisites like custom_task_ids requiring team_id.

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