Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_update_company

Update an existing company record in Autotask, including billing and address fields, with field names matching the REST API.

Instructions

Update an existing company in Autotask. Field names match the Autotask REST API exactly (camelCase, capital ID suffixes where applicable). Note: Autotask uses invoiceTemplateID for payment terms (e.g. 103=Due on Receipt, 104=NET 30) — there is NO paymentTerm field on the Companies entity. Billing address fields (billingAddress1/billToCity/billToState/billToZipCode/billToCountryID/billToAttention/billToAddressToUse) are SEPARATE from the regular address fields (address1/city/state/postalCode/countryID) — set both pairs when needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCompany ID to update
companyNameNoCompany name
phoneNoCompany phone number
address1NoCompany address line 1 (the regular address, distinct from billingAddress1 used for invoices)
address2NoCompany address line 2
cityNoCompany city
stateNoCompany state/province
postalCodeNoCompany postal/ZIP code
countryIDNoCountry ID (e.g. 237 for United States)
isActiveNoWhether the company is active
webAddressNoCompany website URL (Autotask field name is webAddress, not website)
billingAddress1NoBilling address line 1 (used for Invoice Settings — separate from address1)
billingAddress2NoBilling address line 2
billToAttentionNoBill-to attention name
billToAddressToUseNoAddress-to-use flag (1 = 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 provided, so description carries full burden. It discloses field-specific behaviors (e.g., invoiceTemplateID as payment terms, billing address separation) but omits general traits like idempotency, partial update behavior, and error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph of about 5 sentences, front-loaded with main purpose. Informative but slightly dense; could benefit from structured bullet points, but no waste.

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?

Covers key pitfalls (address fields, invoiceTemplateID) but lacks high-level behavioral context such as required fields beyond id, error conditions, or rate limits. With 32 parameters and no output schema, more completeness would be expected.

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?

Schema coverage is 100%, baseline 3. Description adds value by clarifying conventions (camelCase, capital ID suffixes) and explaining critical field relationships (billing vs. regular address, invoiceTemplateID as payment terms).

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?

Clearly states 'Update an existing company in Autotask', providing a specific verb and resource. Does not explicitly differentiate from sibling create tool, but name and description suffice.

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?

No explicit when-to-use or alternatives provided. Usage is implied by the name and context, but no guidance on when to update vs. create or search.

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