AdsAgent — Google Ads MCP

google_ads_accounts_sync

Destructive

Explicitly sync account registration for one owned connection after needs_sync or a live-discovered account is missing from the ledger. Requires mcp.assets.refresh and allow_pull. Reuses account discovery; no metrics/assets pull, Google mutation or MCC linking. Then re-read google_ads_accounts_list before account reads. Do not infer missing Google access from customer_not_owned.

Input Schema

Name	Required	Description	Default
`connection_ref`	Yes
`connection_context`	No

Output Schema

Name	Required	Description	Default
`ok`	No
`code`	No
`error`	No
`needs`	No
`errors`	No
`reason`	No
`ad_count`	No
`next_tool`	No
`retryable`	No
`error_code`	No
`sync_state`	No
`asset_count`	No
`error_count`	No
`next_action`	No
`support_ref`	No
`customer_ids`	No
`ad_group_count`	No
`campaign_count`	No
`connection_ref`	No
`customer_count`	No
`invalid_fields`	No
`rejected_paths`	No
`deferred_reason`	No
`synced_components`	No
`origin_support_ref`	No
`entity_metric_count`	No
`metric_days_written`	No
`enabled_non_manager_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "ad_count": {
+      "type": "integer"
+    },
+    "ad_group_count": {
+      "type": "integer"
+    },
+    "asset_count": {
+      "type": "integer"
+    },
+    "campaign_count": {
+      "type": "integer"
+    },
+    "code": {
+      "type": "string"
+    },
+    "connection_ref": {
+      "type": "string"
+    },
+    "customer_count": {
+      "type": "integer"
+    },
+    "customer_ids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "deferred_reason": {
+      "type": "string"
+    },
+    "enabled_non_manager_count": {
+      "type": "integer"
+    },
+    "entity_metric_count": {
+      "type": "integer"
+    },
+    "error": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "additionalProperties": true,
+              "properties": {
+                "code": {
+                  "type": "string"
+                },
+                "details": {
+                  "additionalProperties": true,
+                  "properties": {},
+                  "type": "object"
+                },
+                "message": {
+                  "type": "string"
+                },
+                "retryable": {
+                  "type": "boolean"
+                },
+                "support_ref": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "error_count": {
+      "type": "integer"
+    },
+    "errors": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "invalid_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "metric_days_written": {
+      "type": "integer"
+    },
+    "needs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_action": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "additionalProperties": true,
+              "properties": {},
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "next_tool": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "origin_support_ref": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "rejected_paths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "support_ref": {
+      "type": "string"
+    },
+    "sync_state": {
+      "type": "string"
+    },
+    "synced_components": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```
AddedOct 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds value by scoping the write to ledger registration and ruling out Google-side mutations and MCC linking, plus naming required permissions. It stops short of saying whether existing ledger entries are overwritten or what a partial sync leaves behind, which matters given destructiveHint=true.

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?

Dense, front-loaded and free of filler: trigger, prerequisites, scope exclusions, follow-up, and a caveat in five short clauses. The customer_not_owned sentence is terse to the point of being cryptic, but it is not padding.

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 two-param mutation tool with an output schema (so return values need not be described), the definition covers preconditions, scope, and post-call behavior well. The remaining gap is the unlabeled connection_context parameter, which leaves the agent guessing on optional input.

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 0%, so the description must carry parameter meaning, and it does not. 'One owned connection' hints that connection_ref identifies the connection, but neither the required connection_ref pattern nor the connection_context token is explained anywhere.

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

Purpose5/5

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

States a specific verb (sync) and resource (account registration for one owned connection), and explicitly delineates what it is not: 'no metrics/assets pull, Google mutation or MCC linking'. That contrast against google_ads_accounts_pull and the mutation tools lets an agent distinguish it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger conditions ('after needs_sync or a live-discovered account is missing from the ledger'), prerequisites ('Requires mcp.assets.refresh and allow_pull'), and a correct follow-up ordering ('re-read google_ads_accounts_list before account reads'). It even warns against a specific wrong inference from customer_not_owned.

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

All AdsAgent — Google Ads MCP 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?