grr

Overview Schema Source Related Servers Discussions Admin

analyticsdata.properties.audienceExports.list

List audience exports for a property to find and reuse existing exports instead of creating unnecessary new ones.

Instructions

Lists all audience exports for a property. This method can be used for you to find and reuse existing audience exports rather than creating unnecessary new audience exports. The same audience can have multiple audience exports that represent the export of users that were in an audience on different days. See Creating an Audience Export for an introduction to Audience Exports with examples. Audience Export APIs have some methods at alpha and other methods at beta stability. The intention is to advance me [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, get, query.

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. All audience exports for this property will be listed in the response. Format: `properties/{property}`
`dry_run`	No	Return the request that would be sent, without sending it.
`pageSize`	No	[query parameter] Optional. The maximum number of audience exports to return. The service may return fewer than this value. If unspecified, at most 200 audience exports will be r
`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 `ListAudienceExports` call. Provide this to retrieve the subsequent page. When paginating, all other parameters

Output Schema

Name	Required	Description	Default
`nextPageToken`	No
`audienceExports`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 26, 2026

changedInput schema / properties / pageSize / description

Previous value: -"Optional. The maximum number of audience exports to return. The service may return fewer than this value. If unspecified, at most 200 audience exports will be r"New value: +"[query parameter] Optional. The maximum number of audience exports to return. The service may return fewer than this value. If unspecified, at most 200 audience exports will be r"

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

changedInput schema / properties / pageToken / description

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

changedInput schema / properties / parent / description

Previous value: -"Required. All audience exports for this property will be listed in the response. Format: `properties/{property}`"New value: +"[URL path segment] Required. All audience exports for this property will be listed in the response. Format: `properties/{property}`"

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "audienceExports": {
+      "items": {
+        "properties": {
+          "audience": {
+            "type": "string"
+          },
+          "audienceDisplayName": {
+            "type": "string"
+          },
+          "beginCreatingTime": {
+            "type": "string"
+          },
+          "creationQuotaTokensCharged": {
+            "type": "integer"
+          },
+          "dimensions": {
+            "items": {
+              "properties": {
+                "dimensionName": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "errorMessage": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "percentageCompleted": {
+            "type": "number"
+          },
+          "rowCount": {
+            "type": "integer"
+          },
+          "state": {
+            "enum": [
+              "STATE_UNSPECIFIED",
+              "CREATING",
+              "ACTIVE",
+              "FAILED"
+            ],
+            "type": "string"
+          }
+        },
+        "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 must carry more behavioral weight. It discloses HTTP GET, JSON output, alpha/beta stability, and generic request-body handling, but does not clearly state permissions, pagination behavior, or explicit side-effect profile.

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 and usage are front-loaded, but the description includes truncated text ("The intention is to advance me") and generic transport boilerplate that does not earn its place for a list operation.

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 and parameter schema coverage is complete, so the description need not explain return values. It adequately covers purpose, reuse rationale, and sibling operations, though it could mention access requirements or pagination context.

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 parameter semantics are already well documented. The description only reinforces generic typed-parameter/body_file behavior and adds no new meaning for parent, pageSize, or pageToken beyond the schema.

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 opens with a specific verb and resource: "Lists all audience exports for a property." It also names the sibling operations (create, get, query), so the agent can distinguish this listing tool from related operations 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 explains the main use case: finding and reusing existing audience exports rather than creating unnecessary new ones. It names siblings, but does not explicitly say when to choose get or query over list, nor does it state exclusions.

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

Deploy Server