Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_update_contact

Update a contact record in Autotask by specifying only the fields to change, such as name, email, phone, address, or custom fields.

Instructions

Update contact record. Only provided fields are changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact ID to update
firstNameNo
lastNameNo
emailAddressNoPrimary email address
phoneNoPrimary phone number
titleNoJob title
isActiveNoWhether the contact is active
mobilePhoneNoMobile phone number
addressLineNoAddress line (primary)
addressLine1NoAddress line 1 (secondary)
cityNoCity
stateNoState/province
zipCodeNoPostal/ZIP code
countryIDNoCountry ID (Autotask Countries entity)
primaryContactNoWhether this contact is the primary contact for their company
userDefinedFieldsNoUser-defined (custom) fields for the contact, as an array of { name, value } objects matching the Autotask REST API shape. Contacts support UDFs (hasUserDefinedFields: true).
Behavior2/5

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

With no annotations provided, the description carries the full burden. It discloses partial update behavior but fails to mention side effects, authorization needs, idempotency, or what happens if the contact ID is invalid. For a mutation tool, more transparency is needed.

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 short sentences, no redundancy, front-loaded with the primary action. Every word serves a purpose; no wasted text.

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 16 parameters and no output schema, the description is minimal. It explains partial update behavior but lacks context on error handling, validation, or relationship to other entities like companies. Adequate but not thorough for a complex tool.

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 88%, so the schema already documents most parameters. The description adds general behavior ('Only provided fields are changed') but no additional parameter-level semantics. Baseline 3 is appropriate.

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 tool's action ('Update contact record') and specifies the partial update behavior ('Only provided fields are changed'). It distinguishes from sibling tools like autotask_create_contact (creation) and autotask_search_contacts (search).

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?

No guidance on when to use this tool versus alternatives (e.g., autotask_create_contact) or context such as prerequisites. The description does not mention when not to use it or any situational cues.

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