Skip to main content
Glama

autotask_update_contact

Update contact details in Autotask by specifying only the fields to change. Modify name, email, phone, address, or activity status.

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 for autotask_update_contact tool. Defines input schema with fields: id (required), 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']
      }
    },
  • Dispatch handler for autotask_update_contact. Calls s.updateContact(a.id, a) on the AutotaskService, passing the contact ID and all provided fields.
    ['autotask_update_contact', async (a) => {
      await s.updateContact(a.id, a); return { result: undefined, message: `Successfully updated contact ID: ${a.id}` };
    }],
  • The updateContact method in AutotaskService. Calls http.update('Contacts', id, updates) to PATCH the Autotask API.
    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;
      }
    }
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that only provided fields are changed (partial update), but does not mention what happens to other fields, if the record is returned, error handling, or any side effects. Partial 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?

Two sentences: first states the action, second clarifies a key behavior. No wasted words, front-loaded. Excellent conciseness.

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?

For a tool with 15 optional parameters and no output schema, the description only covers the partial update behavior. It lacks information about return value, success/failure indicators, error cases, or any required context for successful invocation. 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?

Schema description coverage is 87%, so baseline is 3. The description does not add parameter-specific details beyond the schema, but the general statement 'Only provided fields are changed' provides useful context. No extra value per parameter.

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 'Update contact record' with the verb 'Update' and resource 'contact record', and adds the behavior 'Only provided fields are changed.' This distinguishes it from create and search tools, though it does not explicitly name them.

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

Usage Guidelines3/5

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

The description provides a key usage hint about partial updates ('Only provided fields are changed'), but does not explicitly state when to use this tool versus alternatives like create_contact or search_contacts, nor mention prerequisites like the contact needing to exist.

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