google-ads-mcp-server

Overview Schema Source Related Servers Discussions Admin

google ads get change events

google_ads_get_change_events

Read-onlyIdempotent

Fetch recent Google Ads change events from the last 30 days to audit account modifications, filterable by date range, resource type, operation, or user email.

Instructions

Fetch recent change_event rows. Enforces Google Ads constraints: date window within the last 30 days and LIMIT <= 10000.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`endDate`	No	End date YYYY-MM-DD. Defaults to today.
`operation`	No	Optional ResourceChangeOperation filter, e.g. CREATE, UPDATE, REMOVE
`startDate`	No	Start date YYYY-MM-DD. Defaults to 14 days before endDate.
`userEmail`	No	Optional user email filter
`customerId`	Yes	Google Ads customer ID (without dashes, e.g., 1234567890)
`resourceType`	No	Optional ChangeEventResourceType filter, e.g. CAMPAIGN or AD_GROUP_AD

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.0.0Sep 30, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedv1.0.0Aug 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful behavioral constraints not fully captured by annotations: the date window is limited to the last 30 days and LIMIT cannot exceed 10000. This helps the agent avoid invalid requests.

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?

The description is two short sentences with no filler. The core purpose is front-loaded, and the Google Ads constraint warning is immediately useful without bloating the text.

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

Completeness5/5

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

Given the presence of a full output schema, 100% parameter documentation, and rich annotations, the description is complete enough. It covers the operative purpose and the key external constraints, so an agent has everything needed to select and invoke the tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters and defaults. The description's mention of 'date window' and 'LIMIT <= 10000' largely reiterates schema constraints, adding little semantic value beyond the structured definitions.

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?

The description uses a specific verb ('Fetch') and a specific resource ('change_event rows'), making the tool's purpose immediately clear. It is distinct from siblings because it targets change events specifically, not campaigns, keywords, or other entities.

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

Usage Guidelines4/5

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

The description states the clear context for use: fetching recent change_event rows. It does not explicitly name alternatives or exclusion criteria, but the resource scoping and the 'recent' qualifier provide enough context for an agent to decide when to invoke it.

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

Deploy Server