Skip to main content
Glama
ThatDayneGuy

Autotask MCP Server

by ThatDayneGuy

autotask_create_ticket

Create a new support ticket in Autotask by providing company, title, and description. Optionally set queue, priority, issue type, and more.

Instructions

Create new ticket record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
sourceNoTicket source ID (picklist, e.g. Phone, Email, Portal). Use autotask_get_field_info (entity "Tickets", field "source") to discover valid values.
statusNo
queueIDNoQueue ID to route the ticket to. Use autotask_list_queues to discover valid IDs.
priorityNo
companyIDYesCompany ID for the ticket
contactIDNoContact ID for the ticket
issueTypeNoFirst-level issue type ID (picklist). Required context for subIssueType. Use autotask_get_field_info (entity "Tickets", field "issueType") to discover valid values.
projectIDNoProject ID to associate the ticket with. Links the ticket to an existing project.
resolutionNoTicket-level resolution text. This is the Resolution field on the ticket itself, NOT a ticket note.
ticketTypeNoTicket type ID (picklist, e.g. Service Request, Incident, Problem, Change).
descriptionYes
subIssueTypeNoSub issue type ID (picklist). Must be valid for the selected issueType. Use autotask_get_field_info (entity "Tickets", field "subIssueType") to discover valid values.
billingCodeIDNoWork type / billing code ID used for billing this ticket.
estimatedHoursNoEstimated hours of work for the ticket.
ticketCategoryNoTicket category ID (picklist). Use autotask_get_field_info with entity "Tickets" and field "ticketCategory" to discover valid values.
userDefinedFieldsNoUser-defined (custom) fields for the ticket, as an array of { name, value } objects matching the Autotask REST API shape.
assignedResourceIDNoAssigned resource ID. If set, assignedResourceRoleID is also required by Autotask.
assignedResourceRoleIDNoRole ID for the assigned resource. Required by Autotask when assignedResourceID is set.
serviceLevelAgreementIDNoService Level Agreement (SLA) ID to apply to the ticket.
ticketAdditionalContactsNoAdditional contact IDs to associate with the ticket (beyond the primary contactID).
Behavior2/5

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

No annotations are present, so the description carries full burden. It does not disclose any behavioral traits such as whether the tool returns the created ticket ID, any required permissions, side effects, or potential errors. For a creation tool, this is insufficient.

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?

The description is extremely concise at one sentence, front-loading the purpose. However, it may be too minimal for a complex tool. It is not verbose but lacks necessary context, so a 4 is appropriate.

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

Completeness2/5

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

Given the tool has 21 parameters and no output schema, the description should provide more high-level context about what creating a ticket entails. It does not mention return value, common usage patterns, or dependencies, making it incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no parameter-specific information beyond what the schema already provides. Since schema description coverage is high (81%), the baseline is 3, and the description does not compensate further.

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 'Create new ticket record' clearly states the action (create) and resource (ticket record). The tool name includes 'autotask', and among siblings like autotask_search_tickets and autotask_update_ticket, this tool is unambiguously for creation.

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

Usage Guidelines2/5

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

No usage guidance is provided. There is no mention of when to use this tool versus alternatives like autotask_update_ticket or when not to use it. A simple sentence does not help the agent decide.

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

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