Previous value: -"Array of literal keys, one per level, e.g. [\"actions\",\"Compose\",\"inputs\"]. A \"/\" inside an element is a literal character, so SharePoint/Dataverse column params (flat keys like \"item/Title\") are addressable: [\"actions\",\"Update_Item\",\"inputs\",\"parameters\",\"item/Title\"]. Do NOT pass a slash-delimited string — it cannot distinguish a literal \"/\" from a separator."New value: +"Array of literal keys, one per level, e.g. [\"actions\",\"Compose\",\"inputs\"]. Inside an array, use the item index: [\"actions\",\"Condition\",\"expression\",\"and\",0]. A \"/\" inside an element is a literal character, so SharePoint/Dataverse column params (flat keys like \"item/Title\") are addressable: [\"actions\",\"Update_Item\",\"inputs\",\"parameters\",\"item/Title\"]. Do NOT pass a slash-delimited string — it cannot distinguish a literal \"/\" from a separator."

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "minimum": 0,
+    "type": "integer"
+  }
+]

Removed value: -"string"

Added value: +{
+  "description": "With a whole definition: refuse if the flow changed since you read it. Pass get_live_flow's lastModifiedTime.",
+  "type": "string"
+}

Previous value: -"Connection references map copied from get_live_flow. Direct-flow entries use { connectionName, id }. Solution-aware entries also include { connectionReferenceLogicalName, source } and must retain those fields exactly. A freshly migrated entry may instead be keyed by the physical connection name and carry no connectionName field at all — copy it back as-is. The action/trigger inputs.host.connectionName must match the map key; the physical connectionName stays inside the entry. Never invent a solution logical name. Adding a connectionReferenceLogicalName to an entry that lacks one does not always take: the save can return success without storing it, so re-read with get_live_flow to confirm."New value: +"Connection references map copied from get_live_flow. Direct-flow entries use { connectionName, id }. Solution-aware entries also include { connectionReferenceLogicalName, source } and must retain those fields exactly. A freshly migrated entry may instead be keyed by the physical connection name and carry no connectionName field at all — copy it back as-is. The action/trigger inputs.host.connectionName must match the map key; the physical connectionName stays inside the entry. Never invent a solution logical name. Adding a connectionReferenceLogicalName to an entry that lacks one does not always take: the save can return success without storing it, so re-read with get_live_flow to confirm. MAY BE PASSED ALONGSIDE operations: your entries are merged over the stored map and saved in the SAME request as the edit. That is how you add the first action for a connector the flow does not use yet — a reference saved on its own does not stick, because Power Automate prunes an entry no action references. Your entries win on a key collision."

Previous value: -"Preview only: apply the change to the live definition and return the result + what changed, WITHOUT writing."New value: +"Preview only, on BOTH paths: with flowName, apply the change to the live definition and return the result + what changed; without flowName, return the flow that WOULD be created. Nothing is written either way."

Previous value: -"Connection references map — keyed by logical name (e.g. shared_sharepointonline), each value is { connectionName, id }. Goes into properties.connectionReferences on the PA API call."New value: +"Connection references map copied from get_live_flow. Direct-flow entries use { connectionName, id }. Solution-aware entries also include { connectionReferenceLogicalName, source } and must retain those fields exactly. A freshly migrated entry may instead be keyed by the physical connection name and carry no connectionName field at all — copy it back as-is. The action/trigger inputs.host.connectionName must match the map key; the physical connectionName stays inside the entry. Never invent a solution logical name. Adding a connectionReferenceLogicalName to an entry that lacks one does not always take: the save can return success without storing it, so re-read with get_live_flow to confirm."

Added value: +{
+  "description": "Preview only: apply the change to the live definition and return the result + what changed, WITHOUT writing.",
+  "type": "boolean"
+}

Added value: +{
+  "description": "SURGICAL EDIT of an existing flow (requires flowName; do not combine with definition). An ordered list applied to the LIVE definition. Each item = { op, path, value? }. path is an ARRAY of literal keys, e.g. [\"actions\",\"Send_Email\",\"inputs\",\"parameters\",\"subject\"] (each element is one key; a \"/\" inside an element is literal, so it addresses SharePoint/Dataverse columns like [\"actions\",\"Update_Item\",\"inputs\",\"parameters\",\"item/Title\"]). ops: set (create/overwrite), add (new key — errors if it already exists), remove (delete key — no-op if absent), merge (deep-merge an object value, keeping sibling keys).",
+  "items": {
+    "properties": {
+      "op": {
+        "description": "Edit verb.",
+        "enum": [
+          "set",
+          "add",
+          "remove",
+          "merge"
+        ],
+        "type": "string"
+      },
+      "path": {
+        "description": "Array of literal keys, one per level, e.g. [\"actions\",\"Compose\",\"inputs\"]. A \"/\" inside an element is a literal character, so SharePoint/Dataverse column params (flat keys like \"item/Title\") are addressable: [\"actions\",\"Update_Item\",\"inputs\",\"parameters\",\"item/Title\"]. Do NOT pass a slash-delimited string — it cannot distinguish a literal \"/\" from a separator.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "value": {
+        "description": "New value (required for set/add/merge; merge requires an object)."
+      }
+    },
+    "required": [
+      "op",
+      "path"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Previous value: -"Full flow definition as a JSON object (triggers + actions + parameters + outputs). MUST be a JSON object — strings are rejected. Do not JSON.stringify the definition; pass the parsed object directly. Required when creating. For updates, obtain from get_live_flow (properties.definition), modify it, then pass the modified object here."New value: +"Full flow definition as a JSON object (triggers + actions + parameters + outputs + description). MUST be a JSON object — strings are rejected. Do not JSON.stringify the definition; pass the parsed object directly. Required when creating. For updates, obtain from get_live_flow (properties.definition), modify it, then pass the modified object here. definition.description is required (a short note about what changed); when updating, if you omit it we reuse the flow's existing description."

Removed value: -{
-  "description": "Brief description of what is being changed or created. Required. Will be appended with \"Updated via Flow Studio MCP #flowstudio-mcp\" and stored as the flow description.",
-  "type": "string"
-}

Previous value: -"Full flow definition object (triggers + actions + parameters + outputs). A JSON string is also accepted and will be parsed into an object. Required when creating. For updates, obtain from get_live_flow (properties.definition), modify it, then pass the modified version here."New value: +"Full flow definition as a JSON object (triggers + actions + parameters + outputs). MUST be a JSON object — strings are rejected. Do not JSON.stringify the definition; pass the parsed object directly. Required when creating. For updates, obtain from get_live_flow (properties.definition), modify it, then pass the modified object here."

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