Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_create_time_entry

Record work time in Autotask by creating time entries tied to tickets, tasks, projects, or as regular time for meetings, admin tasks, training, and other categories.

Instructions

Create a time entry in Autotask. Can be tied to a ticket, task, or project, OR created as "Regular Time" (no parent) for meetings, admin work, etc. For Regular Time, specify a category like "Internal Meeting", "Office Management", "Training", etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticketIDNoTicket ID for the time entry (omit for Regular Time)
taskIDNoTask ID for the time entry (for project work, omit for Regular Time)
projectIDNoProject ID for the time entry (omit for Regular Time)
resourceIDNoResource ID (user) logging the time. Can be omitted if resourceName is provided.
resourceNameNoName of the resource/user (e.g., "Will Spence"). Will be resolved to a resourceID automatically. Use this instead of resourceID for convenience.
categoryNoCategory name for Regular Time entries (e.g., "Internal Meeting", "Office Management", "Training", "Research", "HR/Recruiting", "Travel Time", "Holiday", "PTO"). Required for Regular Time entries (when no ticket/task/project is specified).
dateWorkedYesDate worked (YYYY-MM-DD format)
startDateTimeNoStart date/time (ISO format)
endDateTimeNoEnd date/time (ISO format)
hoursWorkedYesNumber of hours worked
summaryNotesYesSummary notes for the time entry
internalNotesNoInternal notes for the time entry
Behavior2/5

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

No annotations provided, so description carries full burden. It only states creation action and possible associations, lacking details on side effects, permissions, error handling, or constraints. Minimal behavioral disclosure.

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?

Three sentences: action, modes, category examples. Front-loaded and efficient with no redundant information.

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?

Lacks explanation of return value, prerequisites, and interplay between time parameters (e.g., start/end vs hours). Incomplete for a complex 12-parameter tool with no output schema or annotations.

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: clarifies mutual exclusivity of ticketID/taskID/projectID vs category, and explains resourceName as convenience alternative to resourceID. This goes beyond schema descriptions.

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 'Create a time entry in Autotask' and distinguishes between entry tied to ticket/task/project and 'Regular Time' with category examples. This differentiates it from sibling create tools.

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 explicitly explains two usage modes (with IDs or as Regular Time with category) and provides category examples. It implicitly guides parameter choice but does not mention alternatives or exclusions.

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