autotask_get_ticket_attachment
Retrieve a ticket attachment from Autotask. Returns metadata by default, or optionally fetch the base64-encoded file content.
Instructions
Get a ticket attachment. With includeData=false (default) returns metadata only — fast, suitable for browsing. With includeData=true returns the base64 binary content via the top-level /TicketAttachments/{id} endpoint (the child endpoint never populates data). The attachment is verified to belong to the given ticketId. Oversized binaries are stripped from the response with a dataOmittedReason field — Autotask attachments can be up to 3 MB, which is ~4 MB as base64 and may exceed the MCP client tool-result limit (~1 MB).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"ticketId": "<ticketId>",
"attachmentId": "<attachmentId>"
},
"name": "autotask_get_ticket_attachment"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ticketId | Yes | The ticket ID the attachment belongs to | |
| includeData | No | Set true to fetch the base64-encoded file bytes. Default false returns metadata only. | |
| attachmentId | Yes | The attachment ID to retrieve | |
| maxInlineBase64Bytes | No | Cap on base64 string length before data is stripped (default 750_000, ~560 KB raw). Only relevant when includeData=true. Raise carefully — your MCP client may reject oversized tool results. |