grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.dataStreams.list

List data streams for a Google Analytics property as JSON, using page size and page token for pagination.

Instructions

Lists DataStreams on a property [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: create, delete, get, 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.
`pageSize`	No	[query parameter] The maximum number of resources to return. If unspecified, at most 50 resources will be returned. The maximum value is 200 (higher values will be coerced to the
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageToken`	No	[query parameter] A page token, received from a previous `ListDataStreams` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provided to `

Output Schema

Name	Required	Description	Default
`dataStreams`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 26, 2026

changedInput schema / properties / pageSize / description

Previous value: -"The maximum number of resources to return. If unspecified, at most 50 resources will be returned. The maximum value is 200 (higher values will be coerced to the"New value: +"[query parameter] The maximum number of resources to return. If unspecified, at most 50 resources will be returned. The maximum value is 200 (higher values will be coerced to the"

addedInput schema / properties / pageSize / format
```
Added value: +"int32"
```

changedInput schema / properties / pageToken / description

Previous value: -"A page token, received from a previous `ListDataStreams` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provided to `"New value: +"[query parameter] A page token, received from a previous `ListDataStreams` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provided to `"

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": {
+    "dataStreams": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description does carry the read-only nature via 'Lists' and '[HTTP GET]', and mentions the JSON return. But the second sentence is generic transport boilerplate about request bodies and body_file that is largely irrelevant—and mildly misleading—for a GET list operation, and it omits any mention of pagination semantics, permissions, or rate limits beyond what the schema already states.

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 clause is correctly front-loaded and short, but the second sentence is shared transport boilerplate (body building, body_file) that does not earn its place on a read-only list endpoint and dilutes the definition.

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?

An output schema exists, so return values need not be explained, and the schema fully covers all seven parameters including the required parent format. What remains thin is the behavioral envelope (pagination flow across pageToken, permission requirements), which keeps it short of a 5.

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 parent, pageSize, pageToken, query, params, dry_run and body_file in detail. The description adds no parameter-level meaning beyond restating the generic typed-parameter/params precedence rule, so the baseline 3 applies.

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 and resource ('Lists DataStreams on a property') and explicitly names the sibling operations (create, delete, get, patch) over the same resource, so an agent can separate this list operation from the single-resource get 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?

Naming the sibling operations gives clear context for what this tool is not, and '[HTTP GET]' plus 'Lists' signals a read path. However, it never states explicitly when to choose list over get (e.g., enumerating all streams vs. fetching one by ID), so the exclusion is implied rather than spelled out.

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

Deploy Server