Skip to main content
Glama
AdLoop: Google Ads, Reddit Ads & GA4

AdLoop: Google Ads, Reddit Ads & GA4

List Analytics audiences

list_ga4_audiences
Read-only

List a GA4 property's audiences and check whether each reaches Google Ads, showing targeting rules, slots used and readiness status for remarketing use.

Instructions

List a GA4 property's audiences and check whether they reach Google Ads.

GA4 shares its audiences with every linked Google Ads account that allows personalized advertising; there they are remarketing lists (get_audience_lists) that draft_audience_attachment puts on a campaign. Returns each audience's resource name, display name, description, membership duration and what includes or excludes users: events, pages (include_pages / exclude_pages: the URL contains the text) or a sequence of steps (audiences built with other conditions in GA4's editor carry custom_conditions and the raw conditions; "All Users" and "Purchasers", which GA4 creates itself, carry predefined), the audience slots used against the limit (100, or 400 on a 360 property), and google_ads_readiness: checks for the Google Ads link, personalized advertising on it, Google signals, consent and list size, each with a status (ok, warn or info). insights repeats the warnings. Reads the GA4 Admin API (audiences.list, googleAdsLinks.list, googleSignalsSettings).

Google Analytics Data API: https://developers.google.com/analytics/devguides/reporting/data/v1 and Admin API: https://developers.google.com/analytics/devguides/config/admin/v1

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_ga4_audiences"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_idNoGA4 property as "properties/123456789" or the bare numeric ID. If empty, uses the default from config.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.45.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds real substance beyond that by disclosing the underlying Admin API calls (audiences.list, googleAdsLinks.list, googleSignalsSettings), the audience-slot limits (100, or 400 on a 360 property), and the specific readiness checks performed with their ok/warn/info statuses. It does not mention auth scopes, permission prerequisites, or failure modes for missing links, which keeps it off a 5.

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 opening sentence is well front-loaded and the interrelated tool names land early, but the middle collapses into a single run-on enumeration of return fields with nested parentheticals ('events, pages (include_pages / exclude_pages: the URL contains the text) or a sequence of steps...') that is hard to parse. Much of that field-level detail duplicates the output schema, and the trailing API documentation URLs add bulk without helping tool selection.

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?

Given an output schema exists, the description need not restate return values, yet it supplies enough context — the Ads sharing model, readiness status vocabulary, slot limits, and upstream APIs — that an agent understands what a call will do and how to interpret it. It is complete for invocation; only permission and error behavior are unstated.

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?

There is a single parameter (property_id) with 100% schema description coverage, including the accepted 'properties/123456789' format and the empty-string default fallback, so the schema already carries the semantic load. The description never mentions property_id or adds format or scoping detail beyond it, which is the baseline-3 case when the schema is complete.

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?

States a specific verb and resource ('List a GA4 property's audiences') and immediately scopes it with 'check whether they reach Google Ads', which is the distinctive capability. It also names the sibling concepts get_audience_lists and draft_audience_attachment and explains how GA4 audiences relate to them, so an agent can separate this listing tool from the Ads-side listing tool without opening either schema.

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 establishes clear context by explaining that GA4 audiences surface in Ads as remarketing lists retrievable via get_audience_lists and attachable via draft_audience_attachment, which effectively routes the agent between tools. It stops short of an explicit when-to-use/when-not-to-use statement or naming a sibling to prefer over this one for a given task, so it sits just below the top band.

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

Deploy Server

Other Tools