grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.patch

Update Google Analytics Admin property details with a PATCH request, specifying the property name, fields to change via updateMask, and the JSON property body.

Instructions

Updates a property [HTTP PATCH] — updates the resource; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON GoogleAnalyticsAdminV1betaProperty object accepting account, createTime, currencyCode, deleteTime, displayName, expireTime, industryCategory, name and 5 more fields; pass it via params or whole via body_file Siblings over the same resource: acknowledgeUserDataCollection, create, delete, get, getDataRetentionSettings, list, runAccessReport, updateDataRetentionSettings.

Input Schema

Name	Required	Description
`name`	Yes	[URL path segment] Identifier. Resource name of this property. Format: properties/{property_id} Example: "properties/1000"
`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.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON GoogleAnalyticsAdminV1betaProperty object.
`updateMask`	No	[query parameter] Required. The list of fields to be updated. Field names must be in snake case (e.g., "field_to_update"). Omitted fields will not be updated. To replace the enti
`request_body`	No	Request body of type GoogleAnalyticsAdminV1betaProperty: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`name`	No
`parent`	No
`account`	No
`timeZone`	No
`createTime`	No
`deleteTime`	No
`expireTime`	No
`updateTime`	No
`displayName`	No
`currencyCode`	No
`propertyType`	No
`serviceLevel`	No
`industryCategory`	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 GoogleAnalyticsAdminV1betaProperty object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type GoogleAnalyticsAdminV1betaProperty: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "account": {
+      "type": "string"
+    },
+    "createTime": {
+      "type": "string"
+    },
+    "currencyCode": {
+      "type": "string"
+    },
+    "deleteTime": {
+      "type": "string"
+    },
+    "displayName": {
+      "type": "string"
+    },
+    "expireTime": {
+      "type": "string"
+    },
+    "industryCategory": {
+      "enum": [
+        "INDUSTRY_CATEGORY_UNSPECIFIED",
+        "AUTOMOTIVE",
+        "BUSINESS_AND_INDUSTRIAL_MARKETS",
+        "FINANCE",
+        "HEALTHCARE",
+        "TECHNOLOGY",
+        "TRAVEL",
+        "OTHER",
+        "ARTS_AND_ENTERTAINMENT",
+        "BEAUTY_AND_FITNESS",
+        "BOOKS_AND_LITERATURE",
+        "FOOD_AND_DRINK",
+        "GAMES",
+        "HOBBIES_AND_LEISURE",
+        "HOME_AND_GARDEN",
+        "INTERNET_AND_TELECOM",
+        "LAW_AND_GOVERNMENT",
+        "NEWS",
+        "ONLINE_COMMUNITIES",
+        "PEOPLE_AND_SOCIETY",
+        "PETS_AND_ANIMALS",
+        "REAL_ESTATE",
+        "REFERENCE",
+        "SCIENCE",
+        "SPORTS",
+        "JOBS_AND_EDUCATION",
+        "SHOPPING"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "parent": {
+      "type": "string"
+    },
+    "propertyType": {
+      "enum": [
+        "PROPERTY_TYPE_UNSPECIFIED",
+        "PROPERTY_TYPE_ORDINARY",
+        "PROPERTY_TYPE_SUBPROPERTY",
+        "PROPERTY_TYPE_ROLLUP"
+      ],
+      "type": "string"
+    },
+    "serviceLevel": {
+      "enum": [
+        "SERVICE_LEVEL_UNSPECIFIED",
+        "GOOGLE_ANALYTICS_STANDARD",
+        "GOOGLE_ANALYTICS_360"
+      ],
+      "type": "string"
+    },
+    "timeZone": {
+      "type": "string"
+    },
+    "updateTime": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedOct 26, 2026

changedInput schema / properties / name / description

Previous value: -"Identifier. Resource name of this property. Format: properties/{property_id} Example: \"properties/1000\""New value: +"[URL path segment] Identifier. Resource name of this property. Format: properties/{property_id} Example: \"properties/1000\""

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

changedInput schema / properties / updateMask / description

Previous value: -"Required. The list of fields to be updated. Field names must be in snake case (e.g., \"field_to_update\"). Omitted fields will not be updated. To replace the enti"New value: +"[query parameter] Required. The list of fields to be updated. Field names must be in snake case (e.g., \"field_to_update\"). Omitted fields will not be updated. To replace the enti"

addedInput schema / properties / updateMask / format
```
Added value: +"google-fieldmask"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "account": {
+      "type": "string"
+    },
+    "createTime": {
+      "type": "string"
+    },
+    "currencyCode": {
+      "type": "string"
+    },
+    "deleteTime": {
+      "type": "string"
+    },
+    "displayName": {
+      "type": "string"
+    },
+    "expireTime": {
+      "type": "string"
+    },
+    "industryCategory": {
+      "enum": [
+        "INDUSTRY_CATEGORY_UNSPECIFIED",
+        "AUTOMOTIVE",
+        "BUSINESS_AND_INDUSTRIAL_MARKETS",
+        "FINANCE",
+        "HEALTHCARE",
+        "TECHNOLOGY",
+        "TRAVEL",
+        "OTHER",
+        "ARTS_AND_ENTERTAINMENT",
+        "BEAUTY_AND_FITNESS",
+        "BOOKS_AND_LITERATURE",
+        "FOOD_AND_DRINK",
+        "GAMES",
+        "HOBBIES_AND_LEISURE",
+        "HOME_AND_GARDEN",
+        "INTERNET_AND_TELECOM",
+        "LAW_AND_GOVERNMENT",
+        "NEWS",
+        "ONLINE_COMMUNITIES",
+        "PEOPLE_AND_SOCIETY",
+        "PETS_AND_ANIMALS",
+        "REAL_ESTATE",
+        "REFERENCE",
+        "SCIENCE",
+        "SPORTS",
+        "JOBS_AND_EDUCATION",
+        "SHOPPING"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "parent": {
+      "type": "string"
+    },
+    "propertyType": {
+      "enum": [
+        "PROPERTY_TYPE_UNSPECIFIED",
+        "PROPERTY_TYPE_ORDINARY",
+        "PROPERTY_TYPE_SUBPROPERTY",
+        "PROPERTY_TYPE_ROLLUP"
+      ],
+      "type": "string"
+    },
+    "serviceLevel": {
+      "enum": [
+        "SERVICE_LEVEL_UNSPECIFIED",
+        "GOOGLE_ANALYTICS_STANDARD",
+        "GOOGLE_ANALYTICS_360"
+      ],
+      "type": "string"
+    },
+    "timeZone": {
+      "type": "string"
+    },
+    "updateTime": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose genuinely useful context: it is a mutation that is refused under readonly profiles, and it returns the API response resource as JSON. It omits permission requirements and update semantics for omitted fields, keeping it below a 5.

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?

Purpose is front-loaded, but the body enumerates fields redundantly with a vague 'and 5 more fields' and appends a long undifferentiated sibling list. Those sentences add bulk without helping selection or invocation.

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?

For a 7-parameter mutation with a nested body and no annotations, the description covers the mutation nature, safety-profile behavior, body composition, and return shape. An output schema exists so return values needn't be detailed, and remaining gaps (updateMask semantics livable in schema) are minor.

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% and nested body fields are fully typed, so the schema already documents every parameter. The description adds only the params-vs-body_file routing hint and a partial field list ('and 5 more fields'), which is marginal over the schema, so the baseline 3 applies.

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 names a specific verb and resource ('Updates a property [HTTP PATCH]') and clarifies it mutates the resource. It lists sibling tools over the same resource but does not distinguish which one an agent should pick, so it stops short of a 5.

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?

It states one real usage condition — 'refused under --readonly safety profiles' — which tells the agent when it will fail. However, it only names siblings without any when-to-use guidance distinguishing patch from updateDataRetentionSettings or the other operations, leaving selection implied.

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

Deploy Server