AdsAgent — Google Ads MCP

google_ads_benchmark_dates

Read-only

Read bounded native benchmark_dates insight. Restricted services require fresh server-verified access and otherwise refuse. No writes or access grants.

Input Schema

Name	Required	Description
`body`	Yes
`customer_id`	Yes	10-digit Google Ads customer id.
`connection_context`	No

Output Schema

Name	Required	Description	Default
`ok`	No
`code`	No
`data`	No
`kind`	No
`error`	No
`needs`	No
`reason`	No
`source`	No
`retryable`	No
`error_code`	No
`request_id`	No
`api_version`	No
`next_action`	No
`observed_at`	No
`support_ref`	No
`availability`	No
`invalid_fields`	No
`rejected_paths`	No
`truncated_fields`	No
`origin_support_ref`	No
`forecast_not_guarantee`	No
`smart_campaign_create_supported`	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": {
+    "api_version": {
+      "type": "string"
+    },
+    "availability": {
+      "type": "string"
+    },
+    "code": {
+      "type": "string"
+    },
+    "data": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "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"
+    },
+    "forecast_not_guarantee": {
+      "type": "boolean"
+    },
+    "invalid_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "needs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_action": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "additionalProperties": true,
+              "properties": {},
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "observed_at": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "origin_support_ref": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "rejected_paths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "request_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "smart_campaign_create_supported": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "support_ref": {
+      "type": "string"
+    },
+    "truncated_fields": {
+      "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 4, 2026

TDQS

C2.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false. The description adds a genuine behavioral fact beyond that: restricted services require fresh server-verified access and will refuse otherwise. The 'no writes or access grants' clause is redundant with the annotations but consistent with them.

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?

Three short sentences, front-loaded with the operation before the access caveat, with little waste. The clipped telegraphic phrasing ('bounded native ... insight') trades clarity for brevity but is not bloated.

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?

An output schema exists, so return values needn't be described, but the tool has three parameters, a nested/empty body object, and four near-identical sibling benchmark tools, none of which the description disambiguates. An agent cannot tell what 'body' should contain or how this differs from its benchmark siblings, leaving the definition materially incomplete.

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 coverage is only 33%: customer_id is documented in the schema, but the empty 'body' object and the 'connection_context' pattern field are unexplained anywhere. The description supplies no parameter meaning at all, so it fails to compensate for the coverage gap, and the empty body object is especially opaque for a caller.

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?

The description names a verb ('Read') and a resource ('benchmark_dates insight'), so the basic operation is inferable. However, 'bounded native ... insight' is jargon, and it does nothing to distinguish this from the four sibling benchmark_* tools (locations, metrics, products, sources) that presumably return different slices of the same data.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus benchmark_locations/metrics/products/sources or audience_dates. The only usage-adjacent sentence describes an access precondition ('requires fresh server-verified access and otherwise refuse') rather than a selection criterion, so the agent gets no real routing guidance.

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?