Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_update_contact

Update a contact record by providing only the fields to change.

Instructions

Update contact record. Only provided fields are changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact ID to update
firstNameNo
lastNameNo
emailAddressNoPrimary email address
phoneNoPrimary phone number
titleNoJob title
isActiveNoWhether the contact is active
mobilePhoneNoMobile phone number
addressLineNoAddress line (primary)
addressLine1NoAddress line 1 (secondary)
cityNoCity
stateNoState/province
zipCodeNoPostal/ZIP code
countryIDNoCountry ID (Autotask Countries entity)
primaryContactNoWhether this contact is the primary contact for their company

Implementation Reference

  • Schema definition and registration of the 'autotask_update_contact' MCP tool. Defines all input properties (id required, plus optional fields like firstName, lastName, emailAddress, phone, title, isActive, mobilePhone, addressLine, addressLine1, city, state, zipCode, countryID, primaryContact).
    {
      name: 'autotask_update_contact',
      description: 'Update contact record. Only provided fields are changed.',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Contact ID to update'
          },
          firstName: {
            type: 'string',
            
          },
          lastName: {
            type: 'string',
            
          },
          emailAddress: {
            type: 'string',
            description: 'Primary email address'
          },
          phone: {
            type: 'string',
            description: 'Primary phone number'
          },
          title: {
            type: 'string',
            description: 'Job title'
          },
          isActive: {
            type: 'boolean',
            description: 'Whether the contact is active'
          },
          mobilePhone: {
            type: 'string',
            description: 'Mobile phone number'
          },
          addressLine: {
            type: 'string',
            description: 'Address line (primary)'
          },
          addressLine1: {
            type: 'string',
            description: 'Address line 1 (secondary)'
          },
          city: {
            type: 'string',
            description: 'City'
          },
          state: {
            type: 'string',
            description: 'State/province'
          },
          zipCode: {
            type: 'string',
            description: 'Postal/ZIP code'
          },
          countryID: {
            type: 'number',
            description: 'Country ID (Autotask Countries entity)'
          },
          primaryContact: {
            type: 'boolean',
            description: 'Whether this contact is the primary contact for their company'
          }
        },
        required: ['id']
      }
    },
  • Handler dispatch entry for 'autotask_update_contact'. Calls AutotaskService.updateContact with the contact id and all args, then returns a success message.
    ['autotask_update_contact', async (a) => {
      await s.updateContact(a.id, a); return { result: undefined, message: `Successfully updated contact ID: ${a.id}` };
    }],
  • Service layer method that performs the actual Autotask API PATCH call via http.update('Contacts', id, updates) to update a contact record.
    async updateContact(id: number, updates: Partial<AutotaskContact>): Promise<void> {
      const http = await this.ensureClient();
      try {
        this.logger.debug(`Updating contact ${id}:`, updates);
        await http.update('Contacts', id, updates as Record<string, any>);
        this.logger.info(`Contact ${id} updated successfully`);
      } catch (error) {
        this.logger.error(`Failed to update contact ${id}:`, error);
        throw error;
      }
    }
  • Type definition for AutotaskContact, representing the data shape used by the update operation.
    export interface AutotaskContact {
      id?: number;
      companyID?: number;
      firstName?: string;
      lastName?: string;
      emailAddress?: string;
      phone?: string;
      title?: string;
      isActive?: number; // Note: autotask-node uses number, not boolean
      createDate?: string;
      lastModifiedDate?: string;
      [key: string]: any;
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It states that only provided fields are changed (implied idempotent partial update), but lacks details on error handling, required permissions, rate limits, or behavior if the contact ID is invalid. The description is too sparse for a mutation tool.

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?

The description is extremely concise—two short sentences, no redundancy. The purpose is immediately clear, and the partial update note is front-loaded. Every word earns its place.

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?

Despite high schema coverage and no nested objects, the tool has 15 parameters and no output schema. The description fails to explain return values, error states, or how to use the id parameter effectively. For a complex update tool, this level of completeness is insufficient.

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 input schema has high description coverage (87%), so the baseline is 3. The description adds a general statement that only provided fields are changed, which applies to all parameters, but does not provide additional value beyond what the schema already offers for individual parameters.

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 clearly states it updates a contact record and notes partial update behavior. While the tool name conveys the same, the description adds specificity about only changing provided fields, which is a useful distinction. It does not explicitly differentiate from other update tools, but the context of the name provides sufficient clarity.

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?

The description only mentions partial update behavior but provides no guidance on when to use this tool vs. alternatives (e.g., autotask_create_contact or autotask_search_contacts). There is no mention of prerequisites, required permissions, or typical use cases.

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