Retrieve existing GA4 audience export snapshots and recurring lists without creating new exports, enabling review and management of current configurations.
List existing GA4 Audience Export snapshots and Recurring Audience Lists without creating new exports.
| Name | Required | Description | Default |
|---|---|---|---|
| pageSize | No | ||
| propertyId | Yes | Numeric GA4 property ID or properties/{id}. | |
| includeRecurring | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of safety disclosure; it explicitly advertises a non-mutating operation ('without creating new exports'). It stops short of describing pagination or response shape, so it is not a full behavioral profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One tight, front-loaded sentence with no filler. The key scoping information ('existing', 'without creating new exports') is in the same clause as the main action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list operation, the description plus schema provide enough to invoke it with just propertyId and optional paging/recurring flags. The absence of an output schema and an explicit pointer to query_audience_export leaves minor gaps, but nothing critical for a correct call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema documents propertyId and gives constraints for pageSize and includeRecurring, while the description's mention of snapshot and recurring lists modestly clarifies includeRecurring. It does not fully compensate for the low schema coverage, but the remaining parameters are conventional and inferable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific action ('List'), a precise resource ('GA4 Audience Export snapshots and Recurring Audience Lists'), and explicitly scopes it to existing items ('without creating new exports'). This clearly distinguishes it from any create/export sibling and from query-style tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the right time to use the tool: when you need to enumerate existing GA4 audience export definitions. It also rules out creation, but it does not name alternatives or state when to use ga4_query_audience_export instead, leaving some routing to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.