Skip to main content
Glama

autotask_update_company

Update a company record in Autotask, including billing and shipping addresses. Set payment terms by selecting an invoice template (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)

Implementation Reference

  • Dispatch table entry in AutotaskToolHandler that routes the 'autotask_update_company' tool name to its handler, which calls s.updateCompany(a.id, a).
    ['autotask_update_company', async (a) => {
      await s.updateCompany(a.id, a); return { result: undefined, message: `Successfully updated company ID: ${a.id}` };
    }],
    ['autotask_get_company_site_configuration', async (a) => {
  • Service-layer implementation of updateCompany: makes a PATCH request to 'Companies' entity via AutotaskHttpClient.update().
    async updateCompany(id: number, updates: Partial<AutotaskCompany>): Promise<void> {
      const http = await this.ensureClient();
      try {
        this.logger.debug(`Updating company ${id}:`, updates);
        await http.update('Companies', id, updates as Record<string, any>);
        this.logger.info(`Company ${id} updated successfully`);
      } catch (error) {
        this.logger.error(`Failed to update company ${id}:`, error);
        throw error;
      }
    }
  • Low-level HTTP helper that PATCHes the entity with an { id, ...fields } body — Autotask's update pattern (no PATCH /{Entity}/{id} route).
    async update(entity: string, id: number, body: Record<string, any>): Promise<void> {
      await this.request<void>('PATCH', `/${entity}`, { id, ...body });
    }
  • Schema definition for autotask_update_company: input schema with all updatable fields (address, billing, tax, invoice settings, ownership). Only 'id' is required.
    {
      name: 'autotask_update_company',
      description: 'Update company record. invoiceTemplateID sets payment terms (103=Due on Receipt, 104=NET 30). Billing address fields separate from regular address.',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            
          },
          companyName: {
            type: 'string',
            
          },
          phone: {
            type: 'string',
            
          },
          address1: {
            type: 'string',
            description: 'Regular address (distinct from billingAddress1)'
          },
          address2: {
            type: 'string',
            
          },
          city: {
            type: 'string',
            
          },
          state: {
            type: 'string',
            
          },
          postalCode: {
            type: 'string',
            
          },
          countryID: {
            type: 'number',
            description: 'e.g. 237 for United States'
          },
          isActive: {
            type: 'boolean',
            
          },
          webAddress: {
            type: 'string',
            description: 'Website URL (field name is webAddress)'
          },
          // ---- Billing-to fields (used for Invoice Settings; SEPARATE from regular address) ----
          billingAddress1: {
            type: 'string',
            description: 'For invoices (separate from address1)'
          },
          billingAddress2: {
            type: 'string',
            description: 'Billing address line 2'
          },
          billToAttention: {
            type: 'string',
            description: 'Bill-to attention name'
          },
          billToAddressToUse: {
            type: 'number',
            description: '1 = use bill-to fields explicitly'
          },
          billToCity: {
            type: 'string',
            description: 'Bill-to city'
          },
          billToState: {
            type: 'string',
            description: 'Bill-to state/province'
          },
          billToZipCode: {
            type: 'string',
            description: 'Bill-to ZIP/postal code'
          },
          billToCountryID: {
            type: 'number',
            description: 'Bill-to country ID'
          },
          billToCompanyLocationID: {
            type: 'number',
            description: 'Bill-to company location ID'
          },
          // ---- Tax / invoice settings ----
          taxRegionID: {
            type: 'number',
            description: 'Tax region ID (capital ID suffix per Autotask convention)'
          },
          invoiceTemplateID: {
            type: 'number',
            description: 'Invoice template ID applied to this company. Acts as the payment-terms selector (e.g. 103=Due on Receipt, 104=NET 30).'
          },
          invoiceMethod: {
            type: 'number',
            description: 'Invoice delivery method picklist ID (e.g. 2=Email)'
          },
          invoiceEmailMessageID: {
            type: 'number',
            description: 'Default email-message template ID used when invoicing this company'
          },
          taxID: {
            type: 'string',
            description: 'Tax registration / FEIN / VAT identifier string'
          },
          isTaxExempt: {
            type: 'boolean',
            description: 'Whether the company is tax-exempt. Note: Autotask field name is `isTaxExempt` — not `taxExempt`.'
          },
          // ---- Quote / PO templates ----
          quoteEmailMessageID: {
            type: 'number',
            description: 'Default email-message template ID used when sending quotes'
          },
          quoteTemplateID: {
            type: 'number',
            description: 'Default quote template ID for this company'
          },
          purchaseOrderTemplateID: {
            type: 'number',
            description: 'Default purchase-order template ID for this company'
          },
          // ---- Ownership / classification ----
          ownerResourceID: {
            type: 'number',
            description: 'Resource ID of the account owner'
          },
          classification: {
            type: 'number',
            description: 'Company classification picklist ID'
          },
          companyType: {
            type: 'number',
            description: 'Company type picklist ID (e.g. Customer, Prospect, Vendor)'
          }
        },
        required: ['id']
      }
    },
  • Intent router that maps natural language queries about updating/editing/modifying a company to the autotask_update_company tool.
    if (/\b(?:update|edit|modify)\b/.test(intent)) {
      const params: Record<string, any> = {};
      if (numbers[0]) params.id = numbers[0];
      return {
        suggestedTool: 'autotask_update_company',
        suggestedParams: params,
        description: 'Update company details',
        requiredParams: !params.id ? ['id'] : [],
      };
Behavior3/5

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

With no annotations, the description partially compensates by explaining that invoiceTemplateID sets payment terms and that billing address fields are separate. However, it omits behavioral details such as whether the update is partial or full, required permissions, or any side effects. The description adds some context but is not comprehensive for a mutation tool.

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?

The description is two short sentences, front-loading the primary action ('Update company record') followed by key behavioral hints. No unnecessary words or repetition. It is appropriately sized for the tool's purpose.

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?

Given 32 parameters, no output schema, and no annotations, the description is insufficient. It lacks information on the return value (e.g., success message, updated object), partial update behavior, error conditions, and prerequisites. The description is too brief for the tool's complexity.

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 high (75%), so the baseline is 3. The description adds little beyond the schema: the invoiceTemplateID payment term mapping is already in the schema, and the billing address separation is also described in the schema. Thus, the description provides minimal additional semantic value.

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,' specifying the verb and resource. It distinguishes from siblings like 'autotask_create_company' by indicating modification rather than creation. The added details about invoiceTemplateID and billing addresses further clarify the tool's specific capabilities.

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 implies usage for updating existing companies but lacks explicit when-to-use or when-not-to-use guidance. It does not mention alternatives like 'autotask_create_company' for creation or 'autotask_search_companies' for retrieval. The required 'id' parameter hints at the need for an existing company, but no direct usage context is provided.

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