Skip to main content
Glama
ddonathan

IT Glue MCP Server

by ddonathan

List IT Glue Organizations

itglue_list_organizations
Read-onlyIdempotent

Retrieve and filter client organizations from IT Glue to access configurations, contacts, passwords, and documentation with pagination and sorting options.

Instructions

List organizations in IT Glue with optional filtering and pagination.

Organizations represent client companies in IT Glue. Each organization contains configurations, contacts, passwords, and other documentation.

Args:

  • page (number): Page number, starting from 1 (default: 1)

  • page_size (number): Items per page, max 1000 (default: 50)

  • name (string): Filter by organization name (partial match)

  • organization_type_id (number): Filter by organization type

  • organization_status_id (number): Filter by status (Active, Inactive, etc.)

  • psa_id (string): Filter by PSA integration ID

  • sort (string): Sort field - name, id, updated_at, created_at

  • sort_direction (string): asc or desc

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

Returns: List of organizations with IDs, names, types, statuses, and IT Glue URLs.

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
nameNoFilter by name (partial match supported)
organization_type_idNoFilter by organization type ID
organization_status_idNoFilter by organization status ID
psa_idNoFilter by PSA integration ID
sortNoField to sort byname
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, destructiveHint=false, openWorldHint=true, and idempotentHint=true, covering safety and idempotency. The description adds valuable behavioral context beyond this: it explains what organizations represent (client companies with specific data types), mentions partial match filtering for 'name', and describes the return format options ('markdown' or 'json'). No contradiction with annotations exists.

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 explanatory context, a parameter list, and return information. It is appropriately sized for a tool with 9 parameters, though the parameter details largely repeat schema information, making some content redundant rather than strictly necessary.

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 (9 parameters, no output schema), the description is mostly complete: it explains the tool's purpose, provides usage context, details parameters and returns, and adds behavioral insights. However, it lacks explicit guidance on pagination behavior (e.g., total pages or item counts) and does not fully differentiate from all sibling tools, leaving minor gaps.

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%, providing detailed parameter documentation. The description adds minimal semantic value beyond the schema: it restates default values and max constraints for 'page' and 'page_size', and clarifies that 'name' filtering uses partial match (already in schema). With high schema coverage, the baseline is 3, and the description does not significantly enhance parameter understanding.

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 ('List organizations in IT Glue') and resource ('organizations'), with additional context that 'Organizations represent client companies in IT Glue' and contain various data types. This distinguishes it from sibling tools like 'itglue_get_organization' (singular retrieval) and 'itglue_create_organization' (creation).

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?

The description provides clear context for when to use this tool: for listing organizations with optional filtering and pagination. It implies usage for bulk retrieval rather than single-item lookups (like 'itglue_get_organization'), but does not explicitly state when NOT to use it or name specific alternatives among siblings.

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