grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.accounts.searchChangeHistoryEvents

Search an account's change history and child resources using filters like action, actor, time range, property, and resource type. Returns matching events as JSON for audits.

Instructions

Searches through all changes to an account or its children given the specified set of filters. Only returns the subset of changes supported by the API. The UI may return additional changes [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON GoogleAnalyticsAdminV1betaSearchChangeHistoryEventsRequest object accepting action, actorEmail, earliestChangeTime, latestChangeTime, pageSize, pageToken, property, resourceType; pass it via params or whole via body_file Siblings over the same resource: delete, get, getDataSharingSettings, list, patch, provisionAccountTicket, runAccessReport.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`account`	Yes	[URL path segment] Required. The account resource for which to return change history resources. Format: accounts/{account} Example: `accounts/100`
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON GoogleAnalyticsAdminV1betaSearchChangeHistoryEventsRequest object.
`request_body`	No	Request body of type GoogleAnalyticsAdminV1betaSearchChangeHistoryEventsRequest: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`nextPageToken`	No
`changeHistoryEvents`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / body_file / description

Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON GoogleAnalyticsAdminV1betaSearchChangeHistoryEventsRequest object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type GoogleAnalyticsAdminV1betaSearchChangeHistoryEventsRequest: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "action": {
+      "items": {
+        "enum": [
+          "ACTION_TYPE_UNSPECIFIED",
+          "CREATED",
+          "UPDATED",
+          "DELETED"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "actorEmail": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "earliestChangeTime": {
+      "type": "string"
+    },
+    "latestChangeTime": {
+      "type": "string"
+    },
+    "pageSize": {
+      "type": "integer"
+    },
+    "pageToken": {
+      "type": "string"
+    },
+    "property": {
+      "type": "string"
+    },
+    "resourceType": {
+      "items": {
+        "enum": [
+          "CHANGE_HISTORY_RESOURCE_TYPE_UNSPECIFIED",
+          "ACCOUNT",
+          "PROPERTY",
+          "FIREBASE_LINK",
+          "GOOGLE_ADS_LINK",
+          "GOOGLE_SIGNALS_SETTINGS",
+          "CONVERSION_EVENT",
+          "MEASUREMENT_PROTOCOL_SECRET",
+          "CUSTOM_DIMENSION",
+          "CUSTOM_METRIC",
+          "DATA_RETENTION_SETTINGS",
+          "DISPLAY_VIDEO_360_ADVERTISER_LINK",
+          "DISPLAY_VIDEO_360_ADVERTISER_LINK_PROPOSAL",
+          "DATA_STREAM",
+          "ATTRIBUTION_SETTINGS"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / account / description

Previous value: -"Required. The account resource for which to return change history resources. Format: accounts/{account} Example: `accounts/100`"New value: +"[URL path segment] Required. The account resource for which to return change history resources. Format: accounts/{account} Example: `accounts/100`"

addedInput schema / properties / account / pattern
```
Added value: +"^accounts/[^/]+$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "changeHistoryEvents": {
+      "items": {
+        "properties": {
+          "actorType": {
+            "enum": [
+              "ACTOR_TYPE_UNSPECIFIED",
+              "USER",
+              "SYSTEM",
+              "SUPPORT"
+            ],
+            "type": "string"
+          },
+          "changeTime": {
+            "type": "string"
+          },
+          "changes": {
+            "items": {
+              "properties": {
+                "action": {
+                  "enum": [
+                    "ACTION_TYPE_UNSPECIFIED",
+                    "CREATED",
+                    "UPDATED",
+                    "DELETED"
+                  ],
+                  "type": "string"
+                },
+                "resource": {
+                  "type": "string"
+                },
+                "resourceAfterChange": {
+                  "properties": {
+                    "account": {
+                      "type": "object"
+                    },
+                    "conversionEvent": {
+                      "type": "object"
+                    },
+                    "dataRetentionSettings": {
+                      "type": "object"
+                    },
+                    "dataStream": {
+                      "type": "object"
+                    },
+                    "firebaseLink": {
+                      "type": "object"
+                    },
+                    "googleAdsLink": {
+                      "type": "object"
+                    },
+                    "measurementProtocolSecret": {
+                      "type": "object"
+                    },
+                    "property": {
+                      "type": "object"
+                    }
+                  },
+                  "type": "object"
+                },
+                "resourceBeforeChange": {
+                  "properties": {
+                    "account": {
+                      "type": "object"
+                    },
+                    "conversionEvent": {
+                      "type": "object"
+                    },
+                    "dataRetentionSettings": {
+                      "type": "object"
+                    },
+                    "dataStream": {
+                      "type": "object"
+                    },
+                    "firebaseLink": {
+                      "type": "object"
+                    },
+                    "googleAdsLink": {
+                      "type": "object"
+                    },
+                    "measurementProtocolSecret": {
+                      "type": "object"
+                    },
+                    "property": {
+                      "type": "object"
+                    }
+                  },
+                  "type": "object"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "changesFiltered": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "string"
+          },
+          "userActorEmail": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully notes that the tool returns only the subset of changes supported by the API and that the UI may return additional changes, and it flags the --readonly safety-profile refusal. However, the parenthetical '[HTTP POST] — creates or triggers a change' is misleading for a search operation and could confuse an agent about mutability.

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

Conciseness3/5

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

The purpose is front-loaded and useful, but the paragraph is long, run-on, and mixes behavioral notes, request-body structure, and sibling listing. Several clauses could be tightened or moved, and the misleading HTTP POST note distracts from the core read-only search purpose.

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 not be explained. The description still omits practical details such as pagination behavior and rate-limit considerations, and the usage-versus-alternatives story is incomplete. It covers the basic shape of the call but leaves gaps for an agent deciding how to use it.

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 nested request-body fields. The description repeats the field names (action, actorEmail, earliestChangeTime, etc.) and explains that they can be passed via `params` or `body_file`, but adds little meaning beyond the schema.

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?

The description states a specific verb and resource: 'Searches through all changes to an account or its children given the specified set of filters.' It distinguishes from siblings by listing the other account-level tools, though it does not explain how each sibling differs. An agent can tell it is a change-history search rather than a general list or get.

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 explicit guidance on when to use this tool versus alternatives. The sibling list names delete, get, list, patch, etc., but does not say which conditions favor searchChangeHistoryEvents over those. The agent must infer usage from the purpose sentence alone.

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

Deploy Server