Skip to main content
Glama
ddonathan

IT Glue MCP Server

by ddonathan

Update IT Glue Contact

itglue_update_contact
Idempotent

Modify contact details in IT Glue by updating fields like name, title, emails, phones, and notes for existing contacts.

Instructions

Update an existing contact in IT Glue.

Args:

  • id (string|number): Contact ID (required)

  • first_name (string): First name

  • last_name (string): Last name

  • title (string|null): Job title

  • contact_type_id (number): Contact type ID

  • location_id (number|null): Location ID

  • important (boolean): Important flag

  • notes (string|null): Notes

  • contact_emails (array): Email addresses (replaces existing)

  • contact_phones (array): Phone numbers (replaces existing)

  • response_format (string): 'markdown' or 'json'

Returns: The updated contact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique ID of the resource
organization_idNoOrganization ID
first_nameNoFirst name
last_nameNoLast name
titleNoJob title
contact_type_idNoContact type ID
location_idNoLocation ID
importantNoMark as important contact
notesNoNotes
contact_emailsNoContact email addresses (replaces existing)
contact_phonesNoContact phone numbers (replaces existing)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior3/5

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

Annotations provide key behavioral hints (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), so the description doesn't need to repeat these. It adds some context by noting that contact_emails and contact_phones arrays 'replace existing' data, which clarifies mutation behavior beyond annotations. However, it lacks details on permissions, rate limits, or 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?

The description is well-structured with a clear opening sentence followed by an 'Args' section. It's appropriately sized for a tool with 12 parameters, though the 'Args' list is somewhat redundant given the schema. Every sentence adds value, and it's front-loaded with the core purpose.

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?

For a mutation tool with 12 parameters and no output schema, the description is adequate but has gaps. Annotations cover safety and idempotency, and the schema documents inputs well. However, the description doesn't explain the return value beyond 'The updated contact' (no format details), and it lacks context on error cases or dependencies, leaving some ambiguity for the agent.

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 100%, so the schema already documents all parameters thoroughly. The description lists parameters but adds minimal extra meaning beyond the schema (e.g., noting 'replaces existing' for arrays, which is also in the schema). It doesn't explain parameter interactions or provide examples, staying at the baseline for high schema coverage.

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?

The description clearly states the verb ('Update') and resource ('existing contact in IT Glue'), making the purpose immediately understandable. It distinguishes from siblings like 'itglue_create_contact' by specifying it's for existing contacts, though it doesn't explicitly contrast with other update tools like 'itglue_update_organization'.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing the contact ID), when to use 'itglue_create_contact' instead, or how it differs from other update tools in the sibling list. The agent must infer usage from the name and description alone.

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/ddonathan/itglue-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server