Google Analytics 4 MCP

ga4_list_audiences

Read-only

List audiences on a GA4 property to retrieve their metadata and IDs for use as dimensions in audience-based report breakdowns.

Instructions

List audiences defined on a GA4 property.

Each audience has name, display_name, description, membership_duration_days, ads_personalization_enabled, event_trigger, exclusion_duration_mode, filter_clauses. Reference audienceId as a dimension in run_report for audience-based breakdowns.

NOTE: Uses Admin v1alpha since audiences are still alpha in April 2026.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "property_id": "<property_id>"
    },
    "name": "ga4_list_audiences"
  }
}

Input Schema

Name	Required	Description	Default
`property_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral context by listing the fields returned for each audience and by noting that it 'Uses Admin v1alpha since audiences are still alpha in April 2026,' which helps the agent set expectations about API stability.

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?

The description is compact and front-loaded with the purpose. The field list is useful, and the note about the alpha Admin API is relevant without bloating the text. Every sentence contributes something meaningful.

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 one simple required parameter, an output schema available, and clear scope, the description is largely complete. Minor gaps like pagination behavior and authentication requirements are not mentioned, but they are less critical for this straightforward read-only listing tool.

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 coverage is 0%, but the single required parameter, property_id, is self-describing with title 'Property Id' and is referenced in the description as 'a GA4 property.' The description does not specify the expected format (e.g., numeric property ID vs. full resource name), so it only partially compensates for the missing schema description.

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 clearly states the operation: 'List audiences defined on a GA4 property.' This distinguishes it from sibling list tools like ga4_list_custom_metrics and ga4_list_data_streams by naming the specific resource. Even without the annotation title, the verb and resource are explicit.

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?

The description gives concrete guidance on how to use the result, saying to 'Reference audienceId as a dimension in run_report for audience-based breakdowns.' This is a clear usage context, though it does not explicitly list alternatives or when-not-to-use situations, which keeps it just below the top score.

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

Deploy Server