grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.list

Lists child properties under a specified parent account, excluding inaccessible and trashed properties by default, to help you discover and manage analytics properties.

Instructions

Returns child Properties under the specified parent Account. Properties will be excluded if the caller does not have access. Soft-deleted (ie: "trashed") properties are excluded by default. Returns an empty list if no relevant properties are found [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: acknowledgeUserDataCollection, create, delete, get, getDataRetentionSettings, patch, runAccessReport, updateDataRetentionSettings.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`filter`	No	[query parameter] Required. An expression for filtering the results of the request. Fields eligible for filtering are: `parent:`(The resource name of the parent account/property)
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`pageSize`	No	[query parameter] Optional. The maximum number of resources to return. The service may return fewer than this value, even if there are additional pages. If unspecified, at most 5
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageToken`	No	[query parameter] Optional. A page token, received from a previous `ListProperties` call. Provide this to retrieve the subsequent page. When paginating, all other parameters prov
`showDeleted`	No	[query parameter] Whether to include soft-deleted (ie: "trashed") Properties in the results. Properties can be inspected to determine whether they are deleted or not.

Output Schema

Name	Required	Description	Default
`properties`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 26, 2026

changedInput schema / properties / filter / description

Previous value: -"Required. An expression for filtering the results of the request. Fields eligible for filtering are: `parent:`(The resource name of the parent account/property)"New value: +"[query parameter] Required. An expression for filtering the results of the request. Fields eligible for filtering are: `parent:`(The resource name of the parent account/property)"

changedInput schema / properties / pageSize / description

Previous value: -"Optional. The maximum number of resources to return. The service may return fewer than this value, even if there are additional pages. If unspecified, at most 5"New value: +"[query parameter] Optional. The maximum number of resources to return. The service may return fewer than this value, even if there are additional pages. If unspecified, at most 5"

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

changedInput schema / properties / pageToken / description

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

changedInput schema / properties / showDeleted / description

Previous value: -"Whether to include soft-deleted (ie: \"trashed\") Properties in the results. Properties can be inspected to determine whether they are deleted or not."New value: +"[query parameter] Whether to include soft-deleted (ie: \"trashed\") Properties in the results. Properties can be inspected to determine whether they are deleted or not."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "nextPageToken": {
+      "type": "string"
+    },
+    "properties": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "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 provided, the description carries the behavioral burden and discloses important traits: access-based filtering, default exclusion of soft-deleted properties, empty-list behavior, and that the operation is an HTTP GET. It does not mention authentication requirements or rate limits, but it covers the operation's key read-only and filtering behavior.

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 core purpose and filtering behavior are front-loaded and useful. However, the generic sentence about request bodies built from typed parameters or body_file is largely irrelevant for a GET list operation, and the long sibling enumeration adds bulk without routing guidance.

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 eight parameters, 100% schema coverage, and an output schema, the description is reasonably complete. It covers the key behavioral constraints an agent needs before calling the tool, though it could be stronger by explicitly clarifying pagination behavior or relationship to sibling tools.

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 all eight parameters in detail. The description adds some contextual meaning around the parent account and soft-deleted properties, but it does not materially extend parameter semantics beyond what the schema provides.

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 states a specific verb and resource: it returns child Properties under a specified parent Account. This clearly implies a list operation, but it does not explicitly differentiate when to use it versus sibling operations such as get, create, or delete. The sibling list at the end is named but not contrasted.

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 description gives useful context: properties the caller cannot access are excluded, soft-deleted properties are excluded by default, and an empty list is returned when none are found. However, it does not explicitly say when to use this list operation versus the sibling get or search tools, nor does it state prerequisites or exclusions for alternatives.

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

Deploy Server