AdsAgent — Google Ads MCP

approval_plan_deny

Destructive

Discard a prepared or quota-waiting mixed approval, preserving completed receipts; no Google changes.

Input Schema

Name	Required	Description	Default
`approval_ref`	Yes
`connection_context`	No
`expected_plan_digest`	Yes

Output Schema

Name	Required	Description	Default
`ok`	No
`code`	No
`error`	No
`items`	No
`needs`	No
`state`	No
`reason`	No
`changes`	No
`summary`	No
`platform`	No
`receipts`	No
`retry_at`	No
`retryable`	No
`error_code`	No
`expires_at`	No
`approved_at`	No
`next_action`	No
`plan_digest`	No
`support_ref`	No
`approval_ref`	No
`presentation`	No
`invalid_fields`	No
`rejected_paths`	No
`expected_changes`	No
`origin_support_ref`	No
`instruction_template_id`	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": {
+    "approval_ref": {
+      "type": "string"
+    },
+    "approved_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "changes": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "code": {
+      "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"
+    },
+    "expected_changes": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "expires_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "instruction_template_id": {
+      "type": "string"
+    },
+    "invalid_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "index": {
+            "type": "integer"
+          },
+          "operation": {
+            "type": "string"
+          },
+          "receipt": {
+            "additionalProperties": true,
+            "properties": {},
+            "type": "object"
+          },
+          "state": {
+            "type": "string"
+          },
+          "summary": {
+            "additionalProperties": true,
+            "properties": {},
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "needs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_action": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "additionalProperties": true,
+              "properties": {},
+              "type": "object"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "origin_support_ref": {
+      "type": "string"
+    },
+    "plan_digest": {
+      "type": "string"
+    },
+    "platform": {
+      "type": "string"
+    },
+    "presentation": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "receipts": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "rejected_paths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "retry_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "state": {
+      "type": "string"
+    },
+    "summary": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "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"
+}
```
AddedOct 12, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, so the description's real contribution is scoping that destruction: completed receipts are preserved and no Google-side changes occur, telling the agent the blast radius is local plan state only. It stops short of saying whether denial is reversible or what the output reports.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence, no filler: action, valid states, preservation guarantee, and side-effect boundary in a single clause chain.

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?

Output schema exists so return values need no explanation, and the safety profile is well covered. But for a destructive mutation on a plan, the absence of any parameter guidance and any statement about recovery or subsequent plan state leaves real gaps.

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% across three parameters, and the description says nothing about approval_ref or expected_plan_digest. The digest in particular carries concurrency semantics (stale-plan rejection) that the agent must infer entirely from the name.

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?

Specific verb+resource: 'Discard a ... mixed approval'. The state qualifiers ('prepared or quota-waiting') separate it from approval_plan_confirm, which would act on a plan rather than discard it, though no sibling is named explicitly.

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?

The precondition states are implied ('prepared or quota-waiting'), which tells the agent when denial is valid, but the description never routes to approval_plan_confirm for the alternative path or states what to do on a digest mismatch or on other plan states.

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?