Soclo

Update ad

soclo_ads_update_ad

DestructiveIdempotent

Soclo Ads: Update ad. Spending/deletion: preview, then owner-approved confirm:true with the same requestId. Claim live only when status is active. Fields: soclo://tools/soclo_ads_update_ad.

Input Schema

Name	Required	Description
`confirm`	No	True only after owner approval of spending/deletion preview.
`payload`	Yes
`platform`	No
`accountId`	Yes
`requestId`	No	Reuse this request ID for confirmation and outcome recovery.
`parameters`	Yes
`adAccountId`	No	Advertiser/ad account selected from your Soclo connection.
`expectedCurrency`	No	Approved preview currency, e.g. GBP.
`expectedBudgetType`	No	Approved preview budget type: daily or lifetime.
`expectedBudgetAmount`	No	Approved preview amount; changes require a new preview.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedOct 25, 2026

addedInput schema / definitions

Added value: +{
+  "s1": {
+    "items": {
+      "properties": {
+        "key": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "key"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "s2": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "properties": {
+          "matchType": {
+            "enum": [
+              "exact",
+              "phrase",
+              "broad"
+            ],
+            "type": "string"
+          },
+          "text": {
+            "maxLength": 80,
+            "type": "string"
+          }
+        },
+        "required": [
+          "text"
+        ],
+        "type": "object"
+      }
+    ]
+  }
+}

removedInput schema / properties / accountId / description
```
Removed value: -"The connected ad account in Soclo."
```
removedInput schema / properties / payload / properties / assetGroup / properties / businessName / description
```
Removed value: -"Replaces the BUSINESS_NAME asset."
```
removedInput schema / properties / payload / properties / assetGroup / properties / finalUrl / description
```
Removed value: -"Replaces the asset group's final URL."
```
removedInput schema / properties / payload / properties / assetGroup / properties / headlines / description
```
Removed value: -"Replaces every HEADLINE asset on the group."
```
removedInput schema / properties / payload / properties / assetGroup / properties / longHeadline / description
```
Removed value: -"Replaces the LONG_HEADLINE asset."
```
removedInput schema / properties / payload / properties / creative / properties / headline / description
```
Removed value: -"Meta and LinkedIn (TikTok has no headline slot)"
```
removedInput schema / properties / payload / properties / demandGen / properties / audience / properties / ageRanges / items / properties / max / description
```
Removed value: -"Omit for no upper bound."
```
removedInput schema / properties / payload / properties / demandGen / properties / callToAction / description
```
Removed value: -"Image and carousel ads only."
```
removedInput schema / properties / payload / properties / demandGen / properties / longHeadlines / description
```
Removed value: -"Video ads only."
```
removedInput schema / properties / payload / properties / demandGen / properties / youtubeVideoIds / description
```
Removed value: -"Video ads only."
```
addedInput schema / properties / payload / properties / targeting / properties / keywords / items / $ref
```
Added value: +"#/definitions/s2"
```

removedInput schema / properties / payload / properties / targeting / properties / keywords / items / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "properties": {
-      "matchType": {
-        "enum": [
-          "exact",
-          "phrase",
-          "broad"
-        ],
-        "type": "string"
-      },
-      "text": {
-        "maxLength": 80,
-        "type": "string"
-      }
-    },
-    "required": [
-      "text"
-    ],
-    "type": "object"
-  }
-]

changedInput schema / properties / payload / properties / targeting / properties / locations / anyOf

Previous value: -[
-  {
-    "items": {
-      "description": "ISO 3166-1 alpha-2 country code.",
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "properties": {
-      "cities": {
-        "items": {
-          "properties": {
-            "key": {
-              "type": "string"
-            },
-            "name": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "key"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "countries": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "metros": {
-        "items": {
-          "properties": {
-            "key": {
-              "type": "string"
-            },
-            "name": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "key"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "regions": {
-        "items": {
-          "properties": {
-            "key": {
-              "type": "string"
-            },
-            "name": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "key"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "zips": {
-        "items": {
-          "properties": {
-            "key": {
-              "type": "string"
-            },
-            "name": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "key"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "properties": {
+      "cities": {
+        "$ref": "#/definitions/s1"
+      },
+      "countries": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "metros": {
+        "$ref": "#/definitions/s1"
+      },
+      "regions": {
+        "$ref": "#/definitions/s1"
+      },
+      "zips": {
+        "$ref": "#/definitions/s1"
+      }
+    },
+    "type": "object"
+  }
+]

addedInput schema / properties / payload / properties / targeting / properties / negativeKeywords / items / $ref
```
Added value: +"#/definitions/s2"
```

removedInput schema / properties / payload / properties / targeting / properties / negativeKeywords / items / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "properties": {
-      "matchType": {
-        "enum": [
-          "exact",
-          "phrase",
-          "broad"
-        ],
-        "type": "string"
-      },
-      "text": {
-        "maxLength": 80,
-        "type": "string"
-      }
-    },
-    "required": [
-      "text"
-    ],
-    "type": "object"
-  }
-]

removedInput schema / properties / platform / description
```
Removed value: -"The campaign platform."
```

Changed1 schema field changedOct 19, 2026
- removedInput schema / properties / payload / properties / budget / properties / amount / description
```
Removed value: -"Minimum varies by platform: TikTok=$20, Pinterest=$5, others=$1"
```
First observedOct 12, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations declare destructiveHint, idempotentHint and openWorldHint, so the safety bar is lower, yet the description still adds real operational context: spending/deletion must pass a preview gate and an owner-approved confirm with the same requestId, and the claim only goes live when status is active. That is genuine process disclosure beyond the annotation flags, though it omits merge-vs-replace behavior and failure/rollback semantics.

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?

Short and front-loaded, which is good, but it is telegraphic to the point of ambiguity ("Claim live only when status is active") and ends with a dangling pointer "Fields: soclo://tools/soclo_ads_update_ad" that conveys no information to the agent. That sentence should carry real content or be removed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, 10-parameter mutation over deeply nested objects with no output schema, so the description carries a lot of weight. It covers the single most important safety path (preview → owner-approved confirm → same requestId) but leaves unclear whether payload fields merge or replace existing ad state, what the expected* parameters enforce, and what a successful response returns.

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 60%, so the baseline is 3. The description only echoes the confirm/requestId pairing that the schema already documents and says nothing about the expectedCurrency / expectedBudgetType / expectedBudgetAmount guardrails or the nested payload groups (creative, demandGen, assetGroup, targeting), which are the hardest part of this tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update ad" is a clear verb+resource, but it largely restates the tool name/title and does not distinguish this from near-siblings like soclo_ads_update_ad_status, soclo_ads_update_ad_creative, or soclo_ads_update_ad_campaign. The agent knows it mutates an ad but not which facets of the payload fall under this tool versus those specialized updaters.

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?

There is real conditional guidance: spending/deletion changes require a preview followed by owner-approved confirm:true with the same requestId. However, it never names an alternative tool, never states when to prefer update_ad vs update_ad_status, and never explains the preview step's own tool. Usage context is implied rather than spelled out.

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

All Soclo 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.

Resources

Need Help?