Skip to main content
Glama

List connectors

list_connectors
Read-onlyIdempotent

List the external services the account can connect to its AI agents (CRM, appointments, store, help desk, payments, invoicing, a lookup table): which are connected, on which AI agents (with the attach status of each), and which actions are enabled. Covers HubSpot, Clientify, Pipedrive, GoHighLevel, DataCRM, Calendly, Cal.com, Shopify, WooCommerce, Zendesk, Freshdesk, Stripe, Mercado Pago, Alegra and Airtable; every one this account can use is listed. Read-only: connecting, replacing a token or disconnecting happens in the dashboard's Connectors gallery, and this tool neither accepts nor returns API tokens.

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_connectors"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them: it states that no API tokens are accepted or returned and that connection management lives in the dashboard, which prevents an agent from expecting write capability here.

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-loads the purpose and returned information before the provider list and the read-only caveat. The long enumeration of vendors is dense but earns its place by defining scope precisely; overall it is tight with little waste.

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?

For a one-optional-parameter read tool with no output schema, the description adequately explains what is returned (connected services, agents, attach status, enabled actions) and what is out of scope (token management). A brief note on return shape or pagination would make it fully complete.

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% for the single optional 'fields' parameter, so the schema already explains its meaning and enum values. The description adds no additional parameter detail, which matches the baseline of 3 when the schema does the heavy lifting.

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?

States a specific verb and resource (list the external services connectable to AI agents) and enumerates what is returned: connection state, which agents, attach status, and enabled actions. The provider list makes scope concrete and distinguishes it from sibling listing 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?

Makes clear this is a read-only listing tool and routes mutation work (connecting, replacing tokens, disconnecting) to the dashboard's Connectors gallery. It does not explicitly contrast with a sibling such as list_crm_integrations, so the alternative-selection guidance is clear but not exhaustive.

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