grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.dataStreams.patch

Updates an existing Google Analytics data stream on a property using PATCH, with updateMask to change only specified fields and leave omitted fields unchanged.

Instructions

Updates a DataStream on 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 GoogleAnalyticsAdminV1betaDataStream object accepting androidAppStreamData, createTime, displayName, iosAppStreamData, name, type, updateTime, webStreamData; pass it via params or whole via body_file Siblings over the same resource: create, delete, get, list.

Input Schema

Name	Required	Description
`name`	Yes	[URL path segment] Identifier. Resource name of this Data Stream. Format: properties/{property_id}/dataStreams/{stream_id} Example: "properties/1000/dataStreams/2000"
`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 GoogleAnalyticsAdminV1betaDataStream object.
`updateMask`	No	[query parameter] Required. The list of fields to be updated. Omitted fields will not be updated. To replace the entire entity, use one path with the string "*" to match all fiel
`request_body`	No	Request body of type GoogleAnalyticsAdminV1betaDataStream: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`name`	No
`type`	No
`createTime`	No
`updateTime`	No
`displayName`	No
`webStreamData`	No
`iosAppStreamData`	No
`androidAppStreamData`	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 GoogleAnalyticsAdminV1betaDataStream object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type GoogleAnalyticsAdminV1betaDataStream: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "androidAppStreamData": {
+      "properties": {
+        "firebaseAppId": {
+          "type": "string"
+        },
+        "packageName": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "createTime": {
+      "type": "string"
+    },
+    "displayName": {
+      "type": "string"
+    },
+    "iosAppStreamData": {
+      "properties": {
+        "bundleId": {
+          "type": "string"
+        },
+        "firebaseAppId": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "DATA_STREAM_TYPE_UNSPECIFIED",
+        "WEB_DATA_STREAM",
+        "ANDROID_APP_DATA_STREAM",
+        "IOS_APP_DATA_STREAM"
+      ],
+      "type": "string"
+    },
+    "updateTime": {
+      "type": "string"
+    },
+    "webStreamData": {
+      "properties": {
+        "defaultUri": {
+          "type": "string"
+        },
+        "firebaseAppId": {
+          "type": "string"
+        },
+        "measurementId": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedOct 26, 2026

changedInput schema / properties / name / description

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

addedInput schema / properties / name / pattern

Added value: +"^properties/[^/]+/dataStreams/[^/]+$"

changedInput schema / properties / updateMask / description

Previous value: -"Required. The list of fields to be updated. Omitted fields will not be updated. To replace the entire entity, use one path with the string \"*\" to match all fiel"New value: +"[query parameter] Required. The list of fields to be updated. Omitted fields will not be updated. To replace the entire entity, use one path with the string \"*\" to match all fiel"

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "androidAppStreamData": {
+      "properties": {
+        "firebaseAppId": {
+          "type": "string"
+        },
+        "packageName": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "createTime": {
+      "type": "string"
+    },
+    "displayName": {
+      "type": "string"
+    },
+    "iosAppStreamData": {
+      "properties": {
+        "bundleId": {
+          "type": "string"
+        },
+        "firebaseAppId": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "DATA_STREAM_TYPE_UNSPECIFIED",
+        "WEB_DATA_STREAM",
+        "ANDROID_APP_DATA_STREAM",
+        "IOS_APP_DATA_STREAM"
+      ],
+      "type": "string"
+    },
+    "updateTime": {
+      "type": "string"
+    },
+    "webStreamData": {
+      "properties": {
+        "defaultUri": {
+          "type": "string"
+        },
+        "firebaseAppId": {
+          "type": "string"
+        },
+        "measurementId": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "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, the description carries the full burden. It discloses that the operation is refused under --readonly safety profiles, describes the return value (the API's response resource as JSON), and explains the request body structure and two submission methods (params or body_file). It does not mention permissions or rate limits, but these are minor gaps given the disclosure of the safety restriction.

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?

The description is front-loaded with the core action and resource, then packs in safety, return format, body structure, and sibling context in a single dense but waste-free sentence.

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?

Given the tool's complexity (mutation, nested request body, no annotations), the description covers the key procedural and behavioral points: safety profile refusal, return value, body handling, and sibling operations. It omits some details like updateMask semantics, but the schema covers those.

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 baseline is 3. The description repeats the request body field names and explains that the body can be passed via `params` or `body_file`, but this largely duplicates existing schema descriptions rather than adding significant new meaning.

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 states a specific verb ('Updates') and resource ('DataStream on a property') with HTTP method, and explicitly lists the sibling operations (create, delete, get, list) so an agent can distinguish it without opening the schema.

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?

By naming the sibling operations create/delete/get/list, it implies this tool is for partial updates rather than creation or retrieval. It does not explicitly state when to prefer patch over update or when not to use it, but the context is clear enough.

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

Deploy Server