Skip to main content
Glama
WYRE-AI

Autotask MCP Server

by WYRE-AI

autotask_update_company

Update company records to configure payment terms via invoice template, billing address, tax exemption, and other settings.

Instructions

Update company record. invoiceTemplateID sets payment terms (103=Due on Receipt, 104=NET 30). Billing address fields separate from regular address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
cityNo
phoneNo
stateNo
taxIDNoTax registration / FEIN / VAT identifier string
address1NoRegular address (distinct from billingAddress1)
address2No
isActiveNo
countryIDNoe.g. 237 for United States
billToCityNoBill-to city
postalCodeNo
webAddressNoWebsite URL (field name is webAddress)
billToStateNoBill-to state/province
companyNameNo
companyTypeNoCompany type picklist ID (e.g. Customer, Prospect, Vendor)
isTaxExemptNoWhether the company is tax-exempt. Note: Autotask field name is `isTaxExempt` — not `taxExempt`.
taxRegionIDNoTax region ID (capital ID suffix per Autotask convention)
billToZipCodeNoBill-to ZIP/postal code
invoiceMethodNoInvoice delivery method picklist ID (e.g. 2=Email)
classificationNoCompany classification picklist ID
billToAttentionNoBill-to attention name
billToCountryIDNoBill-to country ID
billingAddress1NoFor invoices (separate from address1)
billingAddress2NoBilling address line 2
ownerResourceIDNoResource ID of the account owner
quoteTemplateIDNoDefault quote template ID for this company
invoiceTemplateIDNoInvoice template ID applied to this company. Acts as the payment-terms selector (e.g. 103=Due on Receipt, 104=NET 30).
billToAddressToUseNo1 = use bill-to fields explicitly
quoteEmailMessageIDNoDefault email-message template ID used when sending quotes
invoiceEmailMessageIDNoDefault email-message template ID used when invoicing this company
billToCompanyLocationIDNoBill-to company location ID
purchaseOrderTemplateIDNoDefault purchase-order template ID for this company

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.31.0
  2. Removedv2.30.0
  3. Addedv2.26.0
  4. Removedv2.25.5
  5. Changed13 schema fields changedv2.24.4
    • changedInput schema / properties / address1 / description
      Previous value: -"Company address line 1 (the regular address, distinct from billingAddress1 used for invoices)"New value: +"Regular address (distinct from billingAddress1)"
    • removedInput schema / properties / address2 / description
      Removed value: -"Company address line 2"
    • changedInput schema / properties / billToAddressToUse / description
      Previous value: -"Address-to-use flag (1 = use bill-to fields explicitly)"New value: +"1 = use bill-to fields explicitly"
    • changedInput schema / properties / billingAddress1 / description
      Previous value: -"Billing address line 1 (used for Invoice Settings — separate from address1)"New value: +"For invoices (separate from address1)"
    • removedInput schema / properties / city / description
      Removed value: -"Company city"
    • removedInput schema / properties / companyName / description
      Removed value: -"Company name"
    • changedInput schema / properties / countryID / description
      Previous value: -"Country ID (e.g. 237 for United States)"New value: +"e.g. 237 for United States"
    • removedInput schema / properties / id / description
      Removed value: -"Company ID to update"
    • removedInput schema / properties / isActive / description
      Removed value: -"Whether the company is active"
    • removedInput schema / properties / phone / description
      Removed value: -"Company phone number"
    • removedInput schema / properties / postalCode / description
      Removed value: -"Company postal/ZIP code"
    • removedInput schema / properties / state / description
      Removed value: -"Company state/province"
    • changedInput schema / properties / webAddress / description
      Previous value: -"Company website URL (Autotask field name is webAddress, not website)"New value: +"Website URL (field name is webAddress)"
  6. Addedv2.24.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry full burden. It discloses that invoiceTemplateID sets payment terms and that billing addresses are separate, but leaves out other behavioral traits such as reversibility, required permissions, or response behavior.

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 precisely state the purpose and key behavioral notes. No extraneous information, every sentence adds value.

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 32 parameters and no output schema, the description is relatively brief. It highlights crucial distinctions (payment terms, billing addresses) but does not cover all behavioral aspects comprehensively.

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 75%, so the schema already explains most parameters. The description adds value for invoiceTemplateID (payment terms mapping) and billing address distinction, but this is marginal beyond the schema.

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?

The description clearly states the verb 'update' and the resource 'company record'. It distinguishes from sibling tools like 'autotask_create_company' and 'autotask_search_companies' by focusing on modification.

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 some context (e.g., invoiceTemplateID behaviors) but does not explicitly state when to use this tool versus alternatives like create or search. No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools