Skip to main content
Glama

autotask_update_contact

Update an existing contact in Autotask with partial data—only include fields you want to change.

Instructions

Update an existing contact in Autotask. Pass only the fields you want to change; all non-id fields are optional. Field names match the Autotask REST API exactly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact ID to update
firstNameNoContact first name
lastNameNoContact last name
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
Behavior3/5

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

No annotations exist, so description carries full burden. It discloses partial update and API matching but omits side effects (e.g., deactivation impact), auth needs, or return value. Adequate but not thorough.

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 concise sentences, front-loaded with purpose, no fluff. Perfectly sized.

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?

Tool has 15 params, no output schema, no annotations. Description covers partial update but lacks return value info (e.g., updated object or status). Adequate but could be more complete.

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. The description adds value by clarifying partial update (non-id optional) and API naming, exceeding schema's field-level descriptions.

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 action ('Update'), the resource ('existing contact'), and key behavior (partial update, optional fields, API naming). It distinguishes from sibling create/search tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to pass only fields to change, which guides usage. Lacks explicit when-not-to-use or alternatives, but the partial update instruction is clear and effective.

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