Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_create_ticket_attachment

Upload a file attachment to an existing Autotask ticket by passing base64-encoded content (max 3 MB).

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?

No annotations provided. Description discloses base64 encoding requirement, 3 MB limit, and validation with clear error. Additional details like permissions or idempotency are missing but acceptable.

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?

Two sentences plus a concise example. Front-loaded with purpose, then encoding and limit. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks output schema and does not describe return value (e.g., attachment ID). Adequate for practical use but could be more complete.

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 covers 100% of parameters with descriptions. Description adds example and clarifies base64 encoding for data field, and mentions default for publish, adding value beyond schema.

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 verb 'Upload' and resource 'file attachment to an existing ticket'. Distinguishes from sibling tools like autotask_get_ticket_attachment (retrieve) and autotask_search_ticket_attachments (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?

Description provides clear context: encode file as base64, respects 3 MB limit with validation. Does not explicitly state when not to use or suggest alternatives, but context is sufficient.

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

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