Soclo

Add Search ad-group keywords

soclo_ads_add_ad_keywords

Destructive

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

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`	No
`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.

Changed5 schema fields changedOct 25, 2026

removedInput schema / properties / accountId / description
```
Removed value: -"The connected ad account in Soclo."
```
removedInput schema / properties / payload / properties / adSetId / description
```
Removed value: -"Google ad group ID to add the keywords to"
```

changedInput schema / properties / payload / properties / keywords / items / anyOf

Previous value: -[
-  {
-    "description": "Keyword text; defaults to BROAD match",
-    "type": "string"
-  },
-  {
-    "properties": {
-      "matchType": {
-        "enum": [
-          "exact",
-          "phrase",
-          "broad"
-        ],
-        "type": "string"
-      },
-      "text": {
-        "maxLength": 80,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "text"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "properties": {
+      "matchType": {
+        "enum": [
+          "exact",
+          "phrase",
+          "broad"
+        ],
+        "type": "string"
+      },
+      "text": {
+        "maxLength": 80,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "text"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / properties / payload / properties / negative / description

Removed value: -"Add as ad-group-level negatives instead of positive keywords"

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

First observedOct 12, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Beyond the annotations, the description discloses a preview/approval flow, the need to reuse the same requestId, and that claims should only be considered live when status is active. This adds useful mutation-safety context, though it does not elaborate on spend implications or failure behavior.

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 description is short and front-loads the core purpose and confirmation workflow. The final 'Fields: soclo://...' pointer is cryptic and does not clearly earn its place, but otherwise it is efficient.

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

Completeness2/5

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

This is a complex destructive mutation with 10 parameters, nested payload objects, and no output schema. The description covers the confirmation protocol but leaves key payload semantics, keyword structure, match types, negative keywords, and validation boundaries unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 60%, and the description adds meaning mainly for confirm and requestId. It does not explain the core payload parameters such as adSetId, keywords, matchType, or negative, nor other parameters like platform or accountId.

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 states a specific verb and resource: 'Add Search ad-group keywords.' This is clear, but it does not explicitly differentiate the tool from siblings such as soclo_ads_update_ad_keyword, soclo_ads_remove_ad_keyword, or soclo_ads_list_ad_keywords.

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 gives a confirmation workflow ('preview, then owner-approved confirm:true with the same requestId') and a status condition, which implies when confirmation is appropriate. However, it does not state when to use this tool versus related add/update/remove keyword tools or what prerequisites are required.

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?