Skip to main content
Glama

Connect integration

connect_integration
Destructive

Connect a tool so its people sync in as contacts, in a list of their own, every 6 hours: Mixpanel (projectId, username, secret = a service account; sourceId = cohort id), Amplitude (apiKey, secretKey, sourceId), HubSpot (accessToken), Shopify (shopDomain, accessToken), Salesforce, or a webhook. Takes the event or property that shows people agreed to texts (consentEvent / consentField) and the property that holds their phone (phoneField). Credentials are proved with one read, sealed, and never returned. Mixpanel also takes eventTriggers, which turn Mixpanel events into TextKit events that start, end or branch automations; warnings names mapped events with no volume in 7 days.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "provider": "<provider>"
    },
    "name": "connect_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoMixpanel / Amplitude: pull with credentials every 6 hours (default when credentials are sent), or push: no credentials, the tool's cohort sync posts to the ingest URL.
nameNoWhat to call it (default: the tool and its source).
apiKeyNoAmplitude API key.
regionNoMixpanel / Amplitude data residency.
secretNoMixpanel service account secret.
clientIdNoSalesforce consumer key, or Shopify client id.
providerYesThe tool to connect
sfObjectNoSalesforce: the object to sync
sourceIdNoMixpanel or Amplitude cohort id; HubSpot list id; Salesforce campaign id; a Shopify customer search. Blank = everyone (HubSpot, Shopify, Salesforce).
usernameNoMixpanel service account username.
projectIdNoMixpanel project id.
secretKeyNoAmplitude secret key.
phoneEventNoMixpanel: an event that carries the number when profiles do not (e.g. Verification Check Success). A member with no phone on the profile gets it from their latest such event.
phoneFieldNoThe tool's property holding the mobile number, when not the usual one ($phone, phone, mobilephone).
shopDomainNoShopify store, like acme.myshopify.com.
accessTokenNoHubSpot private app token, or Shopify Admin API access token.
instanceUrlNoSalesforce My Domain URL.
clientSecretNoSalesforce consumer secret, or Shopify client secret.
consentEventNoMixpanel / Amplitude: the opt-in event the cohort is built on (e.g. SMS Opt In). Everyone in the cohort is recorded as opted in, from that event.
consentFieldNoThe tool's property that records SMS consent (e.g. sms_opt_in).
exportEventsNoMixpanel (with a service account): send each text's events onto the person's Mixpanel profile: TextKit Message Sent, Delivered, Failed, Link Clicked, Reply Received and Opted Out, with the message, batch or automation and step ids and names. The person is matched by the batch recipient's external_id, the user id or mixpanel_distinct_id of the event that started the automation, or the contact Mixpanel supplied. On unless false. Needs a service account Mixpanel lets import (Admin or Owner on the project).
eventTriggersNoMixpanel (with a service account): events to turn into TextKit events within about 10 minutes, so automations start, wait and branch on them. Each entry is a TextKit event name and the Mixpanel events that count as it, like { event: "purchase_completed", mixpanel_events: ["Purchase Completed", "Web Trial Successful"] }. Only events from people in the integration's list become events, matched by their Mixpanel id. [] clears them. The answer's `warnings` names mapped events that fired 0 times in the last 7 days.
phoneEventPropertyNoMixpanel: that event's property holding the number (default phone).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / exportEvents
      Added value: +{
      +  "description": "Mixpanel (with a service account): send each text's events onto the person's Mixpanel profile: TextKit Message Sent, Delivered, Failed, Link Clicked, Reply Received and Opted Out, with the message, batch or automation and step ids and names. The person is matched by the batch recipient's external_id, the user id or mixpanel_distinct_id of the event that started the automation, or the contact Mixpanel supplied. On unless false. Needs a service account Mixpanel lets import (Admin or Owner on the project).",
      +  "type": "boolean"
      +}
  2. Changed4 schema fields changed
    • addedInput schema / properties / eventTriggers / items / properties / event / description
      Added value: +"The TextKit event to record"
    • addedInput schema / properties / eventTriggers / items / properties / mixpanel_events / description
      Added value: +"The Mixpanel events that map to it, up to 10"
    • addedInput schema / properties / provider / description
      Added value: +"The tool to connect"
    • addedInput schema / properties / sfObject / description
      Added value: +"Salesforce: the object to sync"
  3. Changed1 schema field changed
    • changedInput schema / properties / eventTriggers / description
      Previous value: -"Mixpanel (with a service account): events to turn into TextKit events within about 10 minutes, so automations start, wait and branch on them. Each entry is a TextKit event name and the Mixpanel events that count as it, like { event: \"purchase_completed\", mixpanel_events: [\"Purchase Completed\", \"Web Trial Successful\"] }. Only events from people in the integration's list become events, matched by their Mixpanel id. [] clears them."New value: +"Mixpanel (with a service account): events to turn into TextKit events within about 10 minutes, so automations start, wait and branch on them. Each entry is a TextKit event name and the Mixpanel events that count as it, like { event: \"purchase_completed\", mixpanel_events: [\"Purchase Completed\", \"Web Trial Successful\"] }. Only events from people in the integration's list become events, matched by their Mixpanel id. [] clears them. The answer's `warnings` names mapped events that fired 0 times in the last 7 days."
  4. Changed1 schema field changed
    • addedInput schema / properties / eventTriggers
      Added value: +{
      +  "description": "Mixpanel (with a service account): events to turn into TextKit events within about 10 minutes, so automations start, wait and branch on them. Each entry is a TextKit event name and the Mixpanel events that count as it, like { event: \"purchase_completed\", mixpanel_events: [\"Purchase Completed\", \"Web Trial Successful\"] }. Only events from people in the integration's list become events, matched by their Mixpanel id. [] clears them.",
      +  "items": {
      +    "properties": {
      +      "event": {
      +        "type": "string"
      +      },
      +      "mixpanel_events": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "maxItems": 10,
      +        "type": "array"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses substantial behavior: credentials are proved with one read, sealed and never returned; the pull cadence is every 6 hours; eventTriggers apply 'within about 10 minutes'; and the response's `warnings` field names events with no volume in 7 days. The one gap is that destructiveHint=true is never explained — it does not say whether connecting over an existing integration replaces or wipes its configuration.

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 sync outcome and cadence are front-loaded, and nearly every clause carries information (provider credential map, consent handling, eventTriggers, warnings). The first sentence is an overloaded run-on with nested parentheses that is harder to parse than it needs to be.

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 23-parameter integration-setup tool with no output schema, the description covers the essential behavioral contract (sync cadence, credential handling, consent fields, event triggers, warnings) well. It stops short on the push/pull mode semantics, Salesforce-only parameters, and what the call returns, but these are largely available in the schema.

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?

With 100% schema description coverage the baseline is 3, but the description adds cross-parameter meaning the schema cannot: it groups which credentials belong together per provider (Mixpanel projectId/username/secret = a service account, Amplitude apiKey/secretKey, HubSpot accessToken, Shopify shopDomain/accessToken). Coverage is uneven — Salesforce (clientId/clientSecret/instanceUrl/sfObject), webhook, and the push/pull `mode` are not addressed in the prose.

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 opens with a concrete verb and outcome ('Connect a tool so its people sync in as contacts, in a list of their own, every 6 hours') and enumerates the exact providers supported, so an agent knows precisely what this does. It never names the adjacent operations (update_integration, sync_integration, disconnect_integration, get_integration) to draw a boundary, so sibling differentiation is left implicit.

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?

It implicitly says when to use it (you have provider credentials and want contacts synced) and gives per-provider setup hints, which is real usage context. But it never states when NOT to use it, what happens if the integration already exists, or that update_integration/sync_integration should be used for later changes or manual syncs.

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.