Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_update_ticket_checklist_item

Update a ticket's checklist item to change its text, mark complete/incomplete, or reorder its position.

Instructions

Update a checklist item on a ticket — edit text, mark complete/incomplete, or change position.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticketIdYesThe parent ticket ID
itemIdYesThe checklist item ID to update
itemNameNoNew text for the checklist item
isCompletedNoMark the item complete (true) or incomplete (false)
positionNoNew ordering position for the item

Implementation Reference

  • Schema definition (inputSchema) and registration entry for the 'autotask_update_ticket_checklist_item' tool. Declares parameters: ticketId (required), itemId (required), itemName, isCompleted, position.
    {
      name: 'autotask_update_ticket_checklist_item',
      description: 'Update a checklist item on a ticket — edit text, mark complete/incomplete, or change position.',
      inputSchema: {
        type: 'object',
        properties: {
          ticketId: {
            type: 'number',
            description: 'The parent ticket ID'
          },
          itemId: {
            type: 'number',
            description: 'The checklist item ID to update'
          },
          itemName: {
            type: 'string',
            description: 'New text for the checklist item'
          },
          isCompleted: {
            type: 'boolean',
            description: 'Mark the item complete (true) or incomplete (false)'
          },
          position: {
            type: 'number',
            description: 'New ordering position for the item'
          }
        },
        required: ['ticketId', 'itemId']
      }
    },
  • Dispatch handler for the tool. Extracts ticketId, itemId, itemName, isCompleted, and position from args and delegates to AutotaskService.updateTicketChecklistItem().
    ['autotask_update_ticket_checklist_item', async (a) => {
      await s.updateTicketChecklistItem(a.ticketId, a.itemId, {
        itemName: a.itemName,
        isCompleted: a.isCompleted,
        position: a.position
      });
      return { result: a.itemId, message: `Successfully updated ticket checklist item ${a.itemId}` };
    }],
  • Service-layer implementation. Calls http.childUpdate('Tickets', ticketId, 'ChecklistItems', itemId, body) to PATCH the checklist item on the Autotask REST API.
    async updateTicketChecklistItem(
      ticketId: number,
      itemId: number,
      data: Partial<AutotaskTicketChecklistItem>
    ): Promise<void> {
      const http = await this.ensureClient();
      try {
        this.logger.debug(`Updating checklist item ${itemId} on ticket ${ticketId}:`, data);
        const body = { ...data, ticketID: ticketId } as Record<string, any>;
        await http.childUpdate('Tickets', ticketId, 'ChecklistItems', itemId, body);
        this.logger.info(`Checklist item ${itemId} updated on ticket ${ticketId}`);
      } catch (error) {
        this.logger.error(`Failed to update checklist item ${itemId} on ticket ${ticketId}:`, error);
        throw error;
      }
    }
  • TypeScript interface for the AutotaskTicketChecklistItem entity, defining the shape of checklist item data used by the update tool.
    export interface AutotaskTicketChecklistItem {
      id?: number;
      ticketID?: number;
      itemName?: string;
      isCompleted?: boolean;
      position?: number;
      completedByResourceID?: number;
      completedDateTime?: string;
      [key: string]: any;
    }
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 the basic operation and update types, lacking details on prerequisites, side effects, auth requirements, or error handling. For a mutation tool, more transparency is needed.

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?

Single sentence of 15 words, front-loading the action and listing specific uses with a dash separator. No unnecessary words, efficiently conveys scope.

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?

Given no annotations and no output schema, the description covers the basic update operations but misses behavioral context like error scenarios, idempotency, or return values. Adequate for simple cases but lacks depth for full understanding.

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% with clear parameter descriptions. The description adds value by grouping parameters into semantic updates (text, completion, position), which helps agents map actions to parameters. Slight improvement over schema alone.

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 the verb 'Update' and resource 'checklist item on a ticket', listing three specific operations: edit text, mark complete/incomplete, change position. This distinguishes it from sibling tools like create, delete, and 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?

The description implies usage for updating existing checklist items, but does not explicitly state when not to use it or mention alternatives. The listing of update types gives context, but lacks explicit 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