Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

analyticsadmin.properties.dataStreams.get

Retrieves a single Google Analytics data stream by its resource name and returns the stream details as JSON for inspection or automation.

Instructions

Lookup for a single DataStream [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, list, patch.

Input Schema

NameRequiredDescriptionDefault
nameYes[URL path segment] Required. The name of the DataStream to get. Example format: properties/1234/dataStreams/5678
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.

Output Schema

NameRequiredDescriptionDefault
nameNo
typeNo
createTimeNo
updateTimeNo
displayNameNo
webStreamDataNo
iosAppStreamDataNo
androidAppStreamDataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Required. The name of the DataStream to get. Example format: properties/1234/dataStreams/5678"New value: +"[URL path segment] Required. The name of the DataStream to get. Example format: properties/1234/dataStreams/5678"
    • addedInput schema / properties / name / pattern
      Added value: +"^properties/[^/]+/dataStreams/[^/]+$"
    • 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"
+}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden; it partially meets this by disclosing '[HTTP GET]' (read-only, no side effects) and that the response is the resource as JSON. It omits auth/permission requirements and rate-limit behavior, and the body_file/typed-parameter machinery is irrelevant noise for a GET.

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?

Front-loaded with the core purpose and a short sibling roster; it is reasonably tight. The request-body/body_file sentence is wasted on a GET endpoint, and the wording is slightly run-on.

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 all five parameters are schema-documented. The description says what the tool does and returns, leaving only minor gaps (permissions, pagination not relevant here); the body_file mention is surplus but not harmful.

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 every parameter is already documented, giving a baseline of 3. The description restates the typed-flags-vs-params precedence and body_file behavior that the schema already explains, adding no new parameter semantics.

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?

States a specific verb+resource: 'Lookup for a single DataStream [HTTP GET]', and enumerates the sibling operations over the same resource (create, delete, list, patch), which helps an agent route away from mutations and the list. It stops short of a full five because 'lookup' is soft and the sibling list is generic boilerplate rather than a scoping distinction.

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?

The sibling enumeration implies 'this is the read-one of the family', but there is no explicit when-to-use versus the list method or when-not guidance. Nothing tells the agent to use list first to discover names, so usage is only implied.

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

Deploy Server

Other Tools