Skip to main content
Glama

autotask_update_company

Update a company record in Autotask. Set payment terms via invoiceTemplateID (e.g., Due on Receipt or NET 30) and manage separate billing address fields.

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

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

No annotations present, so description carries full burden. It discloses that invoiceTemplateID acts as payment terms selector and that billing address fields are separate, providing useful behavioral hints. However, it does not mention destructive potential, required permissions, or any side effects of updates.

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, front-loaded with main action, no redundant text. Each sentence adds meaningful information.

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 too brief. It covers a few key nuances but misses important details like the required 'id' field, special behavior of fields like isTaxExempt (field naming), or what the update returns.

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 baseline is 3. Description adds value by clarifying invoiceTemplateID's dual role and billing address separation, but does not elaborate on many other parameters.

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 'Update company record' providing verb and resource. Differentiates from create_company (creation) and search_companies (search) by the action. Additionally highlights specific fields (invoiceTemplateID, billing address) giving specificity.

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?

Implicit usage is clear from tool name ('update'), but no explicit guidance on when to use vs alternatives like create_company or search_companies. No when-not scenarios mentioned.

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