AdsAgent — Google Ads MCP

setup_get_status

Read-only

Start here. Returns redacted OAuth readiness, capability truth, guide version, and notify-only client skill-pack policy; never token values. Finding an ad, campaign, or creative by name is entities_lookup_by_name, not this tool.

Input Schema

Name	Required	Description	Default
`connection_context`	No

Output Schema

Name	Required	Description	Default
`ok`	No
`mcp`	No
`code`	No
`error`	No
`needs`	No
`oauth`	No
`phase`	No
`reason`	No
`scopes`	No
`overall`	No
`retryable`	No
`error_code`	No
`google_ads`	No
`mcp_scoped`	No
`next_action`	No
`support_ref`	No
`capabilities`	No
`invalid_fields`	No
`rejected_paths`	No
`client_skill_pack`	No
`origin_support_ref`	No
`connection_guidance`	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": {
+    "capabilities": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "client_skill_pack": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "code": {
+      "type": "string"
+    },
+    "connection_guidance": {
+      "type": "string"
+    },
+    "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"
+    },
+    "google_ads": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "invalid_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "mcp": {
+      "additionalProperties": true,
+      "properties": {
+        "guide_version": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "mcp_scoped": {
+      "type": "boolean"
+    },
+    "needs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_action": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "additionalProperties": true,
+              "properties": {},
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "oauth": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "origin_support_ref": {
+      "type": "string"
+    },
+    "overall": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "phase": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "rejected_paths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "scopes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "support_ref": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

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

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds materially new context: output is redacted and never contains token values. It stops short of describing the readiness dimensions or what 'capability truth' entails, so it is strong but not exhaustive beyond the annotations.

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?

Two sentences, front-loaded with the routing cue and no filler. Some phrasing ('capability truth', 'notify-only client skill-pack policy') is dense jargon, but nothing is redundant given the output schema carries the return details.

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?

An output schema exists, so return values need not be explained, and the read-only annotations cover the safety profile; the description supplies the entry-point role and the sibling routing. The only real gap is the undocumented connection_context parameter, which is not covered anywhere in prose.

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% and the single parameter (connection_context, a constrained mctx token) is never mentioned in the description. With low coverage the description is expected to compensate, and it does not, so an agent must infer the parameter's format and purpose from the schema pattern alone.

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 (returns) with a concrete, enumerated set of resources: redacted OAuth readiness, capability truth, guide version, and skill-pack policy. It also explicitly distinguishes itself from entities_lookup_by_name, so an agent can route without opening either schema.

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?

"Start here" gives a clear entry-point cue, and the second sentence names both the excluded use case (finding an ad, campaign, or creative by name) and the correct alternative tool. That is explicit when-to-use plus when-not-to-use 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?