grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.acknowledgeUserDataCollection

Acknowledges user data collection terms for a Google Analytics property, a required step before creating Measurement Protocol secrets. Use it to unblock secret creation via API.

Instructions

Acknowledges the terms of user data collection for the specified property. This acknowledgement must be completed (either in the Google Analytics UI or through this API) before MeasurementProtocolSecret resources may be created [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 GoogleAnalyticsAdminV1betaAcknowledgeUserDataCollectionRequest object accepting acknowledgement; pass it via params or whole via body_file Siblings over the same resource: create, delete, get, getDataRetentionSettings, list, patch, runAccessReport, updateDataRetentionSettings.

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.
`dry_run`	No	Return the request that would be sent, without sending it.
`property`	Yes	[URL path segment] Required. The property for which to acknowledge user data collection.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON GoogleAnalyticsAdminV1betaAcknowledgeUserDataCollectionRequest object.
`request_body`	No	Request body of type GoogleAnalyticsAdminV1betaAcknowledgeUserDataCollectionRequest: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
No arguments

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 GoogleAnalyticsAdminV1betaAcknowledgeUserDataCollectionRequest object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type GoogleAnalyticsAdminV1betaAcknowledgeUserDataCollectionRequest: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "acknowledgement": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / property / description

Previous value: -"Required. The property for which to acknowledge user data collection."New value: +"[URL path segment] Required. The property for which to acknowledge user data collection."

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations present the description carries the full burden, and it does well: it discloses HTTP POST, that it creates/triggers a change, that it is refused under --readonly safety profiles, and that it returns the response resource as JSON. It stops short of noting auth requirements or irreversibility, keeping it at 4.

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?

Purpose and prerequisite are front-loaded, and most sentences carry weight. The trailing sibling enumeration is long and of marginal value, slightly diluting efficiency.

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?

With an output schema present and full schema coverage, the description needn't explain return values and correctly omits detail there. It supplies the key prerequisite and mutation behavior, leaving only minor gaps like auth context.

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 coverage is 100%, so the schema already documents property, params, body_file, and the request_body shape. The description largely restates the params/body_file passing mechanism already captured in the schema and adds little beyond the baseline.

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 (Acknowledges) and resource (the terms of user data collection) scoped to the property, and explicitly names the sibling operations over the same resource so it is distinguishable without opening a schema. The prerequisite relationship to MeasurementProtocolSecret is also surfaced.

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?

Provides strong context for when this is needed (before MeasurementProtocolSecret resources may be created) and names the alternative path (the GA UI or this API). It does not explicitly state when-not to call, so it falls just short of the top tier.

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

Deploy Server