Skip to main content
Glama

Get integration options

get_integration_options
Read-onlyIdempotent

Integrations (between two systems): Use when someone asks what CRM Connector can do, which integrations or systems it offers or supports, whether it can connect a business system, which systems it pairs with, or what travels between two systems: record types, direction (one way or both ways), when a record travels (when paid, won, accepted or overdue), ready rules such as a won deal that becomes a draft invoice, the filters and the extras. Without a system it lists both products of this plugin (integrations between two systems, with every system CRM Connector connects and its partners, and AI Agents inside one system); with one system it lists every partner and what travels; with two it details that pair; for a spreadsheet source (Google Sheets, an Excel or CSV file) it also returns our template made for the other system, with its download link, tabs and columns. It needs no sign in, and every answer carries a link that opens the setup in CRM Connector. Not for setting up an integration with chosen record types (use plan_integration), for which fields travel (use get_integration_fields), for how to connect a system (use get_connection_guide), or for a person's own integrations or sync results. A system not listed here is not supported; send_request can ask for it. Systems available for integrations today: activecampaign (ActiveCampaign), companycam (CompanyCam), spreadsheetfile (Excel or CSV file), freeagent (FreeAgent), freshbooks (FreshBooks), gohighlevel (GoHighLevel), googlesheets (Google Sheets), housecallpro (Housecall Pro), hubspot (HubSpot), jobber (Jobber), keap (Keap), dynamics365 (Microsoft Dynamics 365), monday (monday.com), pipedrive (Pipedrive), quickbooks (QuickBooks), salesforce (Salesforce), servicem8 (ServiceM8), square (Square), stripe (Stripe), teamleader (Teamleader Focus), woocommerce (WooCommerce), xero (Xero), zohobooks (Zoho Books), zohocrm (Zoho CRM), zohoinvoice (Zoho Invoice).

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": "get_integration_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemNoOptional system to look up, by its key as listed in the tool description. Leave it out to list every system CRM Connector connects.
other_systemNoOptional second system: when given, the answer details what travels between the two.

Output Schema

NameRequiredDescriptionDefault
pairYes
sheetYes
systemYes
outcomeYes
summaryYes
systemsYes
aiAccessNo
partnersYes
setUpUrlYes
otherSystemYes
integrationsNo
partnerCountYes
requestIntegrationUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / other_system / enum
      Previous value: -[
      -  "activecampaign",
      -  "companycam",
      -  "freeagent",
      -  "freshbooks",
      -  "gohighlevel",
      -  "googlesheets",
      -  "housecallpro",
      -  "hubspot",
      -  "jobber",
      -  "keap",
      -  "monday",
      -  "pipedrive",
      -  "quickbooks",
      -  "salesforce",
      -  "servicem8",
      -  "spreadsheetfile",
      -  "square",
      -  "stripe",
      -  "woocommerce",
      -  "xero",
      -  "zohobooks",
      -  "zohocrm",
      -  "zohoinvoice"
      -]New value: +[
      +  "activecampaign",
      +  "companycam",
      +  "dynamics365",
      +  "freeagent",
      +  "freshbooks",
      +  "gohighlevel",
      +  "googlesheets",
      +  "housecallpro",
      +  "hubspot",
      +  "jobber",
      +  "keap",
      +  "monday",
      +  "pipedrive",
      +  "quickbooks",
      +  "salesforce",
      +  "servicem8",
      +  "spreadsheetfile",
      +  "square",
      +  "stripe",
      +  "teamleader",
      +  "woocommerce",
      +  "xero",
      +  "zohobooks",
      +  "zohocrm",
      +  "zohoinvoice"
      +]
    • changedInput schema / properties / system / enum
      Previous value: -[
      -  "activecampaign",
      -  "companycam",
      -  "freeagent",
      -  "freshbooks",
      -  "gohighlevel",
      -  "googlesheets",
      -  "housecallpro",
      -  "hubspot",
      -  "jobber",
      -  "keap",
      -  "monday",
      -  "pipedrive",
      -  "quickbooks",
      -  "salesforce",
      -  "servicem8",
      -  "spreadsheetfile",
      -  "square",
      -  "stripe",
      -  "woocommerce",
      -  "xero",
      -  "zohobooks",
      -  "zohocrm",
      -  "zohoinvoice"
      -]New value: +[
      +  "activecampaign",
      +  "companycam",
      +  "dynamics365",
      +  "freeagent",
      +  "freshbooks",
      +  "gohighlevel",
      +  "googlesheets",
      +  "housecallpro",
      +  "hubspot",
      +  "jobber",
      +  "keap",
      +  "monday",
      +  "pipedrive",
      +  "quickbooks",
      +  "salesforce",
      +  "servicem8",
      +  "spreadsheetfile",
      +  "square",
      +  "stripe",
      +  "teamleader",
      +  "woocommerce",
      +  "xero",
      +  "zohobooks",
      +  "zohocrm",
      +  "zohoinvoice"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / other_system / enum
      Previous value: -[
      -  "activecampaign",
      -  "companycam",
      -  "freeagent",
      -  "freshbooks",
      -  "gohighlevel",
      -  "googlesheets",
      -  "housecallpro",
      -  "hubspot",
      -  "jobber",
      -  "keap",
      -  "monday",
      -  "pipedrive",
      -  "quickbooks",
      -  "salesforce",
      -  "servicem8",
      -  "spreadsheetfile",
      -  "square",
      -  "stripe",
      -  "woocommerce",
      -  "xero",
      -  "zohobooks",
      -  "zohocrm"
      -]New value: +[
      +  "activecampaign",
      +  "companycam",
      +  "freeagent",
      +  "freshbooks",
      +  "gohighlevel",
      +  "googlesheets",
      +  "housecallpro",
      +  "hubspot",
      +  "jobber",
      +  "keap",
      +  "monday",
      +  "pipedrive",
      +  "quickbooks",
      +  "salesforce",
      +  "servicem8",
      +  "spreadsheetfile",
      +  "square",
      +  "stripe",
      +  "woocommerce",
      +  "xero",
      +  "zohobooks",
      +  "zohocrm",
      +  "zohoinvoice"
      +]
    • changedInput schema / properties / system / enum
      Previous value: -[
      -  "activecampaign",
      -  "companycam",
      -  "freeagent",
      -  "freshbooks",
      -  "gohighlevel",
      -  "googlesheets",
      -  "housecallpro",
      -  "hubspot",
      -  "jobber",
      -  "keap",
      -  "monday",
      -  "pipedrive",
      -  "quickbooks",
      -  "salesforce",
      -  "servicem8",
      -  "spreadsheetfile",
      -  "square",
      -  "stripe",
      -  "woocommerce",
      -  "xero",
      -  "zohobooks",
      -  "zohocrm"
      -]New value: +[
      +  "activecampaign",
      +  "companycam",
      +  "freeagent",
      +  "freshbooks",
      +  "gohighlevel",
      +  "googlesheets",
      +  "housecallpro",
      +  "hubspot",
      +  "jobber",
      +  "keap",
      +  "monday",
      +  "pipedrive",
      +  "quickbooks",
      +  "salesforce",
      +  "servicem8",
      +  "spreadsheetfile",
      +  "square",
      +  "stripe",
      +  "woocommerce",
      +  "xero",
      +  "zohobooks",
      +  "zohocrm",
      +  "zohoinvoice"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / other_system / enum
      Previous value: -[
      -  "activecampaign",
      -  "companycam",
      -  "freeagent",
      -  "freshbooks",
      -  "gohighlevel",
      -  "googlesheets",
      -  "housecallpro",
      -  "hubspot",
      -  "jobber",
      -  "keap",
      -  "pipedrive",
      -  "quickbooks",
      -  "salesforce",
      -  "servicem8",
      -  "spreadsheetfile",
      -  "square",
      -  "stripe",
      -  "woocommerce",
      -  "xero",
      -  "zohobooks",
      -  "zohocrm"
      -]New value: +[
      +  "activecampaign",
      +  "companycam",
      +  "freeagent",
      +  "freshbooks",
      +  "gohighlevel",
      +  "googlesheets",
      +  "housecallpro",
      +  "hubspot",
      +  "jobber",
      +  "keap",
      +  "monday",
      +  "pipedrive",
      +  "quickbooks",
      +  "salesforce",
      +  "servicem8",
      +  "spreadsheetfile",
      +  "square",
      +  "stripe",
      +  "woocommerce",
      +  "xero",
      +  "zohobooks",
      +  "zohocrm"
      +]
    • changedInput schema / properties / system / enum
      Previous value: -[
      -  "activecampaign",
      -  "companycam",
      -  "freeagent",
      -  "freshbooks",
      -  "gohighlevel",
      -  "googlesheets",
      -  "housecallpro",
      -  "hubspot",
      -  "jobber",
      -  "keap",
      -  "pipedrive",
      -  "quickbooks",
      -  "salesforce",
      -  "servicem8",
      -  "spreadsheetfile",
      -  "square",
      -  "stripe",
      -  "woocommerce",
      -  "xero",
      -  "zohobooks",
      -  "zohocrm"
      -]New value: +[
      +  "activecampaign",
      +  "companycam",
      +  "freeagent",
      +  "freshbooks",
      +  "gohighlevel",
      +  "googlesheets",
      +  "housecallpro",
      +  "hubspot",
      +  "jobber",
      +  "keap",
      +  "monday",
      +  "pipedrive",
      +  "quickbooks",
      +  "salesforce",
      +  "servicem8",
      +  "spreadsheetfile",
      +  "square",
      +  "stripe",
      +  "woocommerce",
      +  "xero",
      +  "zohobooks",
      +  "zohocrm"
      +]
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds genuinely new context: no sign-in is required, every answer carries a setup link, spreadsheet sources also return a downloadable template with tabs and columns, and unsupported systems simply do not appear. It stops short of describing rate limits or pagination, which is minor here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded "Use when" clause is good practice, but the body is a single run-on block of semicolon-chained clauses that is hard to scan. The trailing list of 25 systems largely duplicates the schema enums, with display names being its only added value, and it dominates the length.

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?

An output schema exists, so return values needn't be spelled out, and annotations cover the safety profile. Between the trigger phrases, exclusions, auth note, link guarantee, and unsupported-system behavior, nothing an agent needs to select and call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are already documented per-parameter, so the baseline would be 3. The description earns more by explaining the interaction between the two parameters (one system lists partners and data flows, two systems details that pair) and the special spreadsheet-source return, which the schema does not convey.

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 ("Integrations (between two systems)") and then defines the exact answer shape for zero, one, and two systems, so an agent knows precisely what this returns. It also names the siblings it is not (plan_integration, get_integration_fields, get_connection_guide), making it distinguishable without opening any schema.

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?

Explicit trigger phrases are given ("what CRM Connector can do", "whether it can connect a business system", "what travels between two systems") plus four named exclusions with the alternative tool to use instead. It also handles the negative case: a system not in the list is unsupported and send_request can be used to ask for it.

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