Skip to main content
Glama
ddonathan

IT Glue MCP Server

by ddonathan

List IT Glue Contacts

itglue_list_contacts
Read-onlyIdempotent

Retrieve and filter contact information from IT Glue, including employees, vendors, and key individuals associated with organizations.

Instructions

List contacts in IT Glue with optional filtering.

Contacts represent people associated with organizations - employees, vendors, or other important individuals.

Args:

  • page (number): Page number (default: 1)

  • page_size (number): Items per page (default: 50)

  • organization_id (number): Filter by organization

  • first_name (string): Filter by first name

  • last_name (string): Filter by last name

  • contact_type_id (number): Filter by contact type

  • important (boolean): Filter by important flag

  • sort (string): Sort field

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

Returns: List of contacts with names, titles, and contact information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-indexed)
page_sizeNoNumber of items per page (max 1000)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
organization_idNoFilter by organization ID
first_nameNoFilter by first name (partial match)
last_nameNoFilter by last name (partial match)
contact_type_idNoFilter by contact type ID
importantNoFilter by important flag
psa_idNoFilter by PSA integration ID
sortNoField to sort bylast_name
sort_directionNoSort direction: asc (ascending) or desc (descending)asc
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds useful behavioral context beyond annotations: it explains what contacts represent ('people associated with organizations - employees, vendors, or other important individuals'), mentions pagination behavior through the Args section, and specifies the return format options ('markdown' or 'json'). This provides valuable operational context that annotations don't cover.

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 purpose statement upfront, followed by explanatory context about contacts, then parameter details, and finally return information. It's appropriately sized for an 11-parameter tool. The only minor inefficiency is the Args section duplicating schema information, but overall it's front-loaded and each section earns its place by providing useful context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (11 parameters, no output schema), the description provides good contextual completeness. It explains what contacts are, documents all parameters (albeit redundantly), specifies return format options, and describes what the tool returns ('List of contacts with names, titles, and contact information'). The annotations cover safety aspects well. The main gap is lack of explicit differentiation from sibling tools, but overall this is quite complete for a list operation.

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%, meaning all parameters are well-documented in the schema. The description's Args section repeats parameter information (e.g., 'page (number): Page number (default: 1)') that's already in the schema, adding minimal value. However, it does provide a high-level summary of filtering capabilities ('with optional filtering') and mentions the response_format parameter specifically, which offers some semantic context. Given the comprehensive schema coverage, the baseline of 3 is appropriate.

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 tool 'List contacts in IT Glue with optional filtering' and explains that contacts represent people associated with organizations. This provides a specific verb ('List') and resource ('contacts in IT Glue'). However, it doesn't explicitly differentiate from sibling tools like 'itglue_get_contact' (singular) or 'itglue_create_contact', missing an opportunity to clarify when to use this list tool versus those alternatives.

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 through the phrase 'with optional filtering' and the explanation of what contacts represent, suggesting this is for retrieving multiple contacts. However, it lacks explicit guidance on when to use this tool versus alternatives like 'itglue_get_contact' (for a single contact) or 'itglue_create_contact'. There's no mention of prerequisites or when-not-to-use scenarios, leaving usage context somewhat vague.

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