Skip to main content
Glama

List CRM integrations

list_crm_integrations
Read-onlyIdempotent

List the CRMs this account can keep in sync on its own (GoHighLevel, HubSpot, Pipedrive, DataCRM): which are connected, what each one syncs (syncing, already in words), when it last synced, and its last error code (invalid_token / unauthorized = the token was revoked, missing_scopes = it lacks a permission, webhook_failed = CRM edits are not coming back). crm_edits_setup says how CRM edits reach this account: manual = an administrator pastes the account's inbound webhook URL into the CRM (a GoHighLevel workflow or HubSpot app webhook); that URL contains a secret and is shown only on Settings -> Integrations -> CRM -> , not by this tool. automatic = registered by HellouOne (Pipedrive) or checked every 15 minutes (DataCRM, which has no webhooks); automatic_pending = not registered yet, reconnecting fixes it. These are neither the outgoing webhooks of Settings -> Webhooks nor the Connectors AI agents use mid-chat. Connecting, changing a token or a switch happens in Settings -> Integrations -> CRM.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_crm_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint, and the description adds real behavioral context on top: it decodes the error codes (invalid_token/unauthorized = revoked, missing_scopes, webhook_failed) and states that the inbound webhook URL contains a secret and is deliberately not returned by this tool. It omits ordering/pagination and whether an empty list means 'none supported' vs 'none connected', which keeps it off a 5.

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?

Front-loaded correctly — the verb and returned facts come first, with the interpretive detail (crm_edits_setup values, error codes) following. It is dense but every clause carries information; only the Settings-navigation asides are arguably over-detailed for a read-only list call.

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

Completeness5/5

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

There is no output schema, so the description must describe return values — and it does, field by field, including how to interpret `syncing` and `crm_edits_setup`. For a single-optional-parameter read tool with annotations covering safety, nothing an agent needs to call and interpret it is missing.

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?

The single `fields` parameter is fully documented in the schema (100% coverage, enum of allowed field names), so the schema does the heavy lifting. The description never mentions the projection parameter or the `syncing`/`inbound_mode` field names it maps to, adding no meaning beyond the schema; baseline 3 applies.

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?

Opens with a specific verb and resource ('List the CRMs this account can keep in sync on its own') and enumerates the exact providers plus the returned facts (connection state, what syncs, last sync time, last error code). It also explicitly distinguishes itself from list_connectors ('the Connectors AI agents use mid-chat') and from Settings -> Webhooks, so an agent can tell it apart from the other integration-listing siblings.

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

Usage Guidelines5/5

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

States the when-not conditions concretely: this is not the outgoing webhooks surface and not the Connectors catalog, and connecting/changing a token or switch happens in Settings -> Integrations -> CRM rather than here. The explicit routing away from sibling and UI alternatives leaves little to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources