PixelFlow

Update integration

update_integration

DestructiveIdempotent

Change the settings of an integration connected to a site, such as Stripe or Calendly. Returns the saved settings. Every integration has a label and a fixed value sent with every event. Integrations that report payments also have a product list and a minimum payment amount. When they are set, events are sent only for those products and for payments of at least that amount. Fields left out stay unchanged. null clears a field. A setting the integration does not support is refused. Use it when the user wants to change which events an integration sends or the value sent with them.

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

Input Schema

Name	Required	Description
`label`	No	Display name. null clears it.
`site_id`	Yes	Site to act on, as returned by list_sites.
`fixed_value`	No	Value sent with every event from this integration, in the site's currency. null clears it, so each event carries the integration's own amount.
`product_ids`	No	Integrations that report products only, such as Stripe. Events are sent only for payments of these product ids. null clears the filter, so events are sent for all products.
`integration_id`	Yes	Integration id: the `trigger_id` of an integration row in list_triggers.
`minimum_purchase_value`	No	Integrations that report payment amounts only, such as Stripe. No event is sent for a payment below this amount. null removes the minimum.

Output Schema

Name	Required	Description
`type`	Yes	Integration name, such as stripe.
`label`	Yes	Label after the change.
`fixed_value`	Yes	Fixed value sent with each event. null: the integration's own amount is used.
`product_ids`	Yes	Product ids events are sent for. null: events are sent for all products.
`integration_id`	Yes	Integration id.
`minimum_purchase_value`	Yes	No event is sent for a payment below this amount. null: no minimum.

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedNov 2, 2026

addedInput schema / properties / fixed_value / anyOf

Added value: +[
+  {
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / fixed_value / minimum
```
Removed value: -0
```
removedInput schema / properties / fixed_value / type
```
Removed value: -[
-  "number",
-  "null"
-]
```

addedInput schema / properties / label / anyOf

Added value: +[
+  {
+    "maxLength": 255,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / label / maxLength
```
Removed value: -255
```
removedInput schema / properties / label / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedInput schema / properties / minimum_purchase_value / anyOf

Added value: +[
+  {
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / minimum_purchase_value / minimum
```
Removed value: -0
```
removedInput schema / properties / minimum_purchase_value / type
```
Removed value: -[
-  "number",
-  "null"
-]
```

addedInput schema / properties / product_ids / anyOf

Added value: +[
+  {
+    "items": {
+      "maxLength": 64,
+      "type": "string"
+    },
+    "maxItems": 50,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / product_ids / items

Removed value: -{
-  "maxLength": 64,
-  "type": "string"
-}

removedInput schema / properties / product_ids / maxItems
```
Removed value: -50
```
removedInput schema / properties / product_ids / type
```
Removed value: -[
-  "array",
-  "null"
-]
```

addedOutput schema / properties / fixed_value / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / fixed_value / type
```
Removed value: -[
-  "number",
-  "null"
-]
```

addedOutput schema / properties / label / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / label / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / minimum_purchase_value / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / minimum_purchase_value / type
```
Removed value: -[
-  "number",
-  "null"
-]
```

addedOutput schema / properties / product_ids / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / product_ids / items
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / product_ids / type
```
Removed value: -[
-  "array",
-  "null"
-]
```

Changed19 schema fields changedNov 2, 2026

changedInput schema / properties / fixed_value / description

Previous value: -"Value sent with events from this connection"New value: +"Value sent with every event from this integration, in the site's currency. null clears it, so each event carries the integration's own amount."

addedInput schema / properties / fixed_value / minimum
```
Added value: +0
```

changedInput schema / properties / fixed_value / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedInput schema / properties / integration_id / description

Previous value: -"Integration id from list_triggers"New value: +"Integration id: the `trigger_id` of an integration row in list_triggers."

changedInput schema / properties / integration_id / type
```
Previous value: -"number"New value: +"integer"
```

changedInput schema / properties / label / description

Previous value: -"Name shown for this connection. An empty string clears it"New value: +"Display name. null clears it."

addedInput schema / properties / label / maxLength
```
Added value: +255
```

changedInput schema / properties / label / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / properties / minimum_purchase_value / description

Previous value: -"Stripe only. Purchases below this are ignored"New value: +"Integrations that report payment amounts only, such as Stripe. No event is sent for a payment below this amount. null removes the minimum."

addedInput schema / properties / minimum_purchase_value / minimum
```
Added value: +0
```

changedInput schema / properties / minimum_purchase_value / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedInput schema / properties / product_ids / description

Previous value: -"Stripe product ids, such as prod_abc. Stripe only. An empty list clears the allow-list"New value: +"Integrations that report products only, such as Stripe. Events are sent only for payments of these product ids. null clears the filter, so events are sent for all products."

addedInput schema / properties / product_ids / items / maxLength
```
Added value: +64
```
addedInput schema / properties / product_ids / maxItems
```
Added value: +50
```

changedInput schema / properties / product_ids / type

Previous value: -"array"New value: +[
+  "array",
+  "null"
+]

removedInput schema / properties / site

Removed value: -{
-  "description": "Domain, id, or external id from list_sites",
-  "type": "string"
-}

addedInput schema / properties / site_id

Added value: +{
+  "description": "Site to act on, as returned by list_sites.",
+  "type": "integer"
+}

changedInput schema / required

Previous value: -[
-  "site",
-  "integration_id"
-]New value: +[
+  "site_id",
+  "integration_id"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "fixed_value": {
+      "description": "Fixed value sent with each event. null: the integration's own amount is used.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "integration_id": {
+      "description": "Integration id.",
+      "type": "integer"
+    },
+    "label": {
+      "description": "Label after the change.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "minimum_purchase_value": {
+      "description": "No event is sent for a payment below this amount. null: no minimum.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "product_ids": {
+      "description": "Product ids events are sent for. null: events are sent for all products.",
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "type": {
+      "description": "Integration name, such as stripe.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "integration_id",
+    "type",
+    "label",
+    "fixed_value",
+    "product_ids",
+    "minimum_purchase_value"
+  ],
+  "type": "object"
+}

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing merge semantics ('Fields left out stay unchanged'), null-as-clear semantics, and server-side validation behavior ('A setting the integration does not support is refused'), plus what is returned. This clarifies why destructiveHint=true: nulling the product filter widens which events fire, which annotations alone cannot convey.

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 with the action and examples, then rules (partial update, null, refusal), then when-to-use. Slightly long and the null/clear rule is restated in both prose and per-parameter schema text, but each sentence carries actionable information.

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?

For a 6-parameter mutation with full schema coverage and an output schema, nothing essential is missing: the update model, null handling, failure mode, and applicability conditions are all stated. Return values are noted but need not be expanded given the output 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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter semantics the schema does not: which parameters only apply to payment-reporting integrations and the interaction between product_ids/minimum_purchase_value and which events are emitted. It also explains label and fixed_value as a coupled pair.

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?

States a specific verb and resource ('Change the settings of an integration connected to a site') and grounds it with concrete examples (Stripe, Calendly). It never distinguishes itself from close siblings like update_trigger or disconnect_integration, so an agent must infer that integration != trigger from the id naming alone.

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?

The final sentence gives a real use condition: 'when the user wants to change which events an integration sends or the value sent with them.' It does not say when NOT to use it or point to the alternative tool (e.g., update_trigger for trigger-level settings), which leaves sibling routing to inference.

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

All PixelFlow tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.