google-analytics-mcp-server

by getmcpads-com

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

ga4 list audience exports

ga4_list_audience_exports

Read-onlyIdempotent

List existing GA4 audience export snapshots and recurring audience lists for a property without creating new exports.

Instructions

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

Input Schema

TableJSON 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

TableJSON 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.

Changed3 schema fields changedv2.0.0Sep 30, 2026

addedInput schema / properties / includeRecurring / description

Added value: +"Include recurring audience-export configurations."

addedInput schema / properties / pageSize / description

Added value: +"Maximum items requested per page. Follow the returned pagination information for remaining results."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "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."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedv1.0.0Aug 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description carries a lower burden. It adds a small amount of context by emphasizing 'existing' snapshots and recurring lists, but it doesn't cover pagination behavior or which export states are returned.

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?

One sentence that leads with the action and resource and ends with a clear non-creation caveat. Every clause earns its place; no repeated or redundant content.

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?

For a simple read-only list endpoint with a full output schema and fully documented parameters, the description is largely complete. The only notable gap is the absence of guidance on pagination or the relationship to querying an export, though the schema already explains pagination follow-up.

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 fully documents propertyId, pageSize, and includeRecurring. The description's phrase 'Recurring Audience Lists' faintly echoes includeRecurring but adds no parameter-level detail beyond the schema, matching the baseline.

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?

Description has a specific verb ('List'), a specific resource ('GA4 Audience Export snapshots and Recurring Audience Lists'), and explicitly excludes creation ('without creating new exports'). This makes the tool's role obvious and separates it from mutation or diagnostic siblings.

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 implies usage for retrieving existing exports/lists, but it doesn't name a sibling alternative (e.g., querying or creating exports) or state when to prefer this tool over ga4_query_audience_export. 'Without creating new exports' is a useful non-mutation cue but not explicit routing guidance.

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