Skip to main content
Glama
getterdoneinc

getterdone-mcp-server

Official

upload_attachment

Upload a reference file (image, PDF, or short video) to a task for the assigned worker to access after claiming. Files are stored privately with a time-limited download link.

Instructions

Upload a reference file (image, PDF, or short video) to a task so the assigned worker can access it after claiming. Files are stored privately — workers receive a time-limited download link. Max 5 attachments per task. Task must be open or claimed. Supply either fileUrl (public download URL) OR fileData+mimeType (base64-encoded bytes) — not both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesThe task ID to attach the file to
filenameYesDisplay name for the attachment (e.g. "storefront_reference.jpg")
fileUrlNoA publicly accessible URL to the file (JPEG/PNG/WebP ≤8 MB, PDF ≤25 MB, MP4/WebM/MOV ≤30 MB). The server will download and re-upload it. Use this OR fileData, not both.
fileDataNoBase64-encoded file contents. Use instead of fileUrl for files that cannot be given a public URL (e.g. generated files, private data). Must be accompanied by mimeType.
mimeTypeNoMIME type of the file when using fileData (e.g. "image/jpeg", "application/pdf", "video/mp4"). Required when fileData is provided; ignored when fileUrl is used.
Behavior4/5

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

No annotations exist, so the description carries full burden. It discloses that files are stored privately, workers get time-limited download links, and the fileUrl parameter requires a public URL from which the server downloads. It does not cover error cases or authentication requirements, but the core behavior is well described.

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 4 sentences with no wasted words. Purpose, constraints, and parameter usage are presented upfront. Every sentence adds value.

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?

For a file upload tool with 5 parameters and no output schema, the description covers purpose, file type constraints, storage behavior, parameter choice, and task state requirement. It lacks details on error handling or response format, but this is acceptable given the tool's simplicity.

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?

Schema coverage is 100%, so the description's value is in summarizing the exclusive choice between fileUrl and fileData+mimeType, and the task state requirement. It adds meaningful context beyond the schema's individual parameter descriptions.

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 reference file to a task, specifies allowed file types (image, PDF, short video), and explains worker access via time-limited download links. This distinguishes it from sibling tools which handle tasks, approvals, and account operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage context: files are for assigned workers, tasks must be open or claimed, and there's a 5-attachment limit. It also clarifies the mutually exclusive fileUrl vs fileData+mimeType choice. It does not explicitly state when not to use, but the constraints are clear.

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/getterdoneinc/getterdone-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server