Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_update_company

Update company records in Autotask with separate billing addresses and set payment terms using invoice template IDs (e.g., 103 for Due on Receipt).

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)
Behavior4/5

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

Without annotations, the description effectively discloses key behaviors: the invoiceTemplateID acts as payment term selector with examples (103/104) and clarifies that billing address fields are separate from regular address. This adds value beyond the schema.

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 concisely convey the main action and two important nuances. No unnecessary words.

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?

The description covers two key aspects but is minimal given 32 parameters and no annotations. High schema coverage partly compensates, but the description could mention the required id or other notable fields.

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?

The description adds meaning by explaining the payment term implication of invoiceTemplateID and the separation of billing vs. regular address. With 75% schema coverage, the baseline is 3, and this extra context elevates it to 4.

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 'Update company record' with a specific verb and resource. It distinguishes from sibling tools like create_company by focusing on update and highlights key fields (invoiceTemplateID, billing address).

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 does not provide explicit guidance on when to use this tool versus alternatives (e.g., create_company, search_companies). No context on prerequisites or exclusions is given.

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