Skip to main content
Glama

autotask_create_ticket_attachment

Upload a file attachment to an existing Autotask ticket using base64-encoded content. Validates file size against the 3 MB limit before sending.

Instructions

Upload a file attachment to an existing ticket. The file content must be passed as a base64-encoded string in the data field (MCP is JSON-RPC, so binary bytes must be base64-encoded). Autotask enforces a 3 MB hard limit on ticket attachments; this tool validates the decoded size before calling the API and returns a clear error if the limit is exceeded. Example: { ticketId: 12345, title: "screenshot.png", data: "iVBORw0KGgoAAAANSUhEUgAA..." }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticketIdYesThe ticket ID to attach the file to
titleYesDisplay title for the attachment (typically the filename, e.g. "screenshot.png")
dataYesBase64-encoded file content. Maximum decoded size: 3 MB (Autotask ticket attachment limit). Example: read a file and pass its base64 representation here.
fullPathNoOriginal filename including any path. Defaults to `title` if not provided.
contentTypeNoMIME type of the file (e.g. "image/png", "application/pdf"). Optional.
publishNoVisibility: 1 = All Autotask Users (default), 2 = Internal Users Only
Behavior4/5

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

Discloses encoding constraint, size limit, and validation behavior. No annotations provided, so description fulfills the role well. Could add success response info.

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?

Four succinct sentences with clear structure: purpose, constraint, validation, example. No wasted words.

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?

Covers key aspects for a file upload tool (encoding, size limit). Missing return value info, but outputs are not critical for agent invocation.

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%, but description adds value: explains base64 rationale, default for fullPath, size limit, and example. Exceeds baseline.

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?

Clearly states 'Upload a file attachment to an existing ticket', specifying action, resource, and distinguishing from sibling tools like get/search.

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?

Provides clear context: base64 encoding requirement, 3 MB limit, and example. Does not explicitly mention when not to use or alternatives, but it's well-defined.

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/wyre-technology/autotask-mcp'

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