Skip to main content
Glama

autotask_create_ticket

Create a new ticket in Autotask PSA by specifying company, title, description, and optional details like priority, queue, and assignment.

Instructions

Create new ticket record

Input Schema

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

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

The description does not disclose any behavioral traits beyond the bare action. Without annotations, it should explain side effects, authentication needs, rate limits, or what happens on creation (e.g., returns ticket ID). None are provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (4 words), which is under-specified. It sacrifices necessary detail for brevity, making it minimally informative.

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

Completeness1/5

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

For a tool with 21 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain what the tool returns, key inter-parameter dependencies (e.g., assignedResourceID requires assignedResourceRoleID), or success/failure behavior.

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 schema covers 81% of parameters with descriptions, so the baseline is 3. The description adds no extra parameter meaning, but the schema itself is reasonably comprehensive. However, fields like 'title' lack schema descriptions, and the description does not compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 the resource (ticket record). It is specific and distinct from sibling tools that create notes or attachments, though it does not explicitly differentiate from other create tools like autotask_create_task.

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 guidance is provided on when to use this tool versus alternatives, such as autotask_update_ticket or autotask_search_tickets. There is no mention of prerequisites, typical use cases, or scenarios to avoid.

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