grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.dataStreams.create

Creates a Google Analytics data stream for a specified property, supporting web, Android app, or iOS app stream details and returning the API response as JSON.

Instructions

Creates a DataStream [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 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: delete, get, list, patch.

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.
`parent`	Yes	[URL path segment] Required. Example format: properties/1234
`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.
`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"
+}

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / parent / description

Previous value: -"Required. Example format: properties/1234"New value: +"[URL path segment] Required. Example format: properties/1234"

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

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 behavioral burden and does well: it identifies the operation as HTTP POST, states that it creates or triggers a change, discloses refusal under --readonly safety profiles, and says it returns the API response resource as JSON. It still omits required permissions or rate-limit behavior, 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.

Conciseness4/5

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

The key purpose and safety-profile constraint are front-loaded, and every part of the description is relevant. The single long sentence is dense and somewhat run-on, but it avoids filler and keeps useful details.

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 a mutation with a nested request body, full schema description coverage, and an output schema, the description is largely complete: it covers body shape, params/body_file usage, sibling operations, and readonly refusal. It does not mention authorization or required roles, which leaves a small completeness gap.

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 GoogleAnalyticsAdminV1betaDataStream body type and the params/body_file split, both of which are already documented in the schema, so it adds little parameter meaning beyond structured fields.

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 and resource — 'Creates a DataStream' — and immediately names the sibling operations delete, get, list, and patch over the same resource. An agent can distinguish this create tool from the other data stream tools without inspecting schemas.

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?

It gives a clear when-not condition: the operation is refused under --readonly safety profiles. It also lists sibling operations over the same resource as alternatives, though it does not explicitly route the agent between create and patch for existing resources.

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

Deploy Server