Google Analytics 4 by Get MCP Ads

ga4 list audience exports

ga4_list_audience_exports

Read-onlyIdempotent

List existing GA4 Audience Export snapshots and recurring audience lists by property ID without creating new exports.

Instructions

List existing GA4 Audience Export snapshots and Recurring Audience Lists without creating new exports.

Input Schema

Name	Required	Description
`pageSize`	No	Maximum items requested per page. Follow the returned pagination information for remaining results.
`propertyId`	Yes	Numeric GA4 property ID or properties/{id}.
`includeRecurring`	No	Include recurring audience-export configurations.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered structurally. The description's only added context is the 'without creating new exports' reassurance, which reinforces but does not extend the annotation set; it says nothing about rate limits, permissions, or snapshot freshness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single sentence with the resource identified up front and the negative constraint placed at the end where it disambiguates rather than buries the main point. No filler.

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?

With an output schema present, return values need no explanation, and annotations carry the safety profile. The remaining minor gap is that an agent must consult the schema to learn about pagination and the includeRecurring toggle, which the description could have surfaced.

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%, with pageSize, propertyId, and includeRecurring each documented including defaults and bounds. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 (list) and specific resources (GA4 Audience Export snapshots and Recurring Audience Lists), which is far more informative than the title's restatement. The 'without creating new exports' clause implicitly distinguishes it from the creation/query path used by siblings like ga4_query_audience_export, though it never names a sibling outright.

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?

Usage is implied rather than stated: the reader infers this is the read/inspect path and that export creation belongs elsewhere. There is no explicit 'use X when you want to create an export' routing to ga4_query_audience_export, and no prerequisite or pagination-follow-up guidance in the description itself.

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