Skip to main content
Glama

Update integration

update_integration
Destructive

Rename, pause or resume (status), or change an integration's settings or credentials (left-out credentials keep the stored ones). eventTriggers (Mixpanel) maps Mixpanel events to TextKit events; exportEvents: false stops sending text events to Mixpanel (on by default); changing only those does not re-test credentials or resync.

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": {
      "id": "<id>"
    },
    "name": "update_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIntegration id
nameNoWhat to call it
apiKeyNoAmplitude API key
secretNoMixpanel service account secret
statusNoactive, or paused to stop syncing
sourceIdNoMixpanel or Amplitude cohort id; HubSpot list id; Salesforce campaign id; a Shopify customer search
usernameNoMixpanel service account username
secretKeyNoAmplitude secret key
phoneEventNoMixpanel: an event that carries the number when profiles do not
phoneFieldNoThe tool's property holding the mobile number
accessTokenNoHubSpot private app token, or Shopify Admin API access token
consentEventNoMixpanel / Amplitude: the opt-in event the cohort is built on
consentFieldNoThe tool's property that records SMS consent
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. Changing only these keeps the credentials and the sync schedule as they are (no re-test, no resync). 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. Changed15 schema fields changed
    • addedInput schema / properties / accessToken / description
      Added value: +"HubSpot private app token, or Shopify Admin API access token"
    • addedInput schema / properties / apiKey / description
      Added value: +"Amplitude API key"
    • addedInput schema / properties / consentEvent / description
      Added value: +"Mixpanel / Amplitude: the opt-in event the cohort is built on"
    • addedInput schema / properties / consentField / description
      Added value: +"The tool's property that records SMS consent"
    • 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 / name / description
      Added value: +"What to call it"
    • addedInput schema / properties / phoneEvent / description
      Added value: +"Mixpanel: an event that carries the number when profiles do not"
    • addedInput schema / properties / phoneEventProperty / description
      Added value: +"Mixpanel: that event's property holding the number (default phone)"
    • addedInput schema / properties / phoneField / description
      Added value: +"The tool's property holding the mobile number"
    • addedInput schema / properties / secret / description
      Added value: +"Mixpanel service account secret"
    • addedInput schema / properties / secretKey / description
      Added value: +"Amplitude secret key"
    • addedInput schema / properties / sourceId / description
      Added value: +"Mixpanel or Amplitude cohort id; HubSpot list id; Salesforce campaign id; a Shopify customer search"
    • addedInput schema / properties / status / description
      Added value: +"active, or paused to stop syncing"
    • addedInput schema / properties / username / description
      Added value: +"Mixpanel service account username"
  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. Changing only these keeps the credentials and the sync schedule as they are (no re-test, no resync). 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.7/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=false, so the bar is lower, but the description still adds real behavior: partial updates preserve omitted credentials, credential changes trigger a re-test and resync while trigger-only changes do not, exportEvents defaults to on, and '[] clears them' warns of a destructive array operation. It also discloses a return-value detail (`warnings` naming mapped events that fired 0 times in 7 days) despite having no output schema.

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 core operations are front-loaded in the first clause and every sentence carries information, with no filler. It is dense and semicolon-heavy, and the eventTriggers/exportEvents caveats run together, which slightly hurts scannability.

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 16-parameter destructive mutation with no output schema, the description covers the highest-risk behaviors (credential preservation, resync/re-test triggers, clearing arrays) and even names a response field. Gaps remain around permission requirements and what a credential re-test/resync actually does to in-flight syncs, but nothing essential to calling it correctly 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?

Schema coverage is 100%, so the baseline is 3 and the schema already documents all 16 parameters thoroughly. The description adds genuine meaning beyond it for two fields — exportEvents being on by default and eventTriggers accepting [] to clear plus a no-retest/no-resync effect — but says nothing extra about the many credential and field-mapping parameters (apiKey, secret, accessToken, phoneEvent, consentField, sourceId), which are left entirely to the schema.

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 concrete verbs and resources — 'Rename, pause or resume (status), or change an integration's settings or credentials' — so an agent knows exactly which mutation surface this tool covers. It does not explicitly distinguish itself from connect_integration, disconnect_integration, or sync_integration, leaving the agent to infer the boundary from the names alone.

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?

Usage is implied rather than stated: 'left-out credentials keep the stored ones' signals partial-update semantics, and the note that changing only eventTriggers/exportEvents does not re-test or resync tells the agent when a lightweight update is safe. However, there is no explicit when-to-use versus connect_integration, disconnect_integration, or sync_integration, and no stated prerequisites such as required permissions.

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.