AdCopilot

Google Ads: list audiences

list_audiences

Read-onlyIdempotent

Lists the account's audiences and where its campaigns use them.

Returns the audience lists (open or closed, size range, whether each is
eligible for Search and Display, match rate for customer lists), custom
and combined audiences, and for each enabled or paused campaign its
audience setting (OBSERVATION, TARGETING or NOT_SET) and the audiences
attached at campaign or ad group level, with clicks, conversions and
cost. An ad group audience also carries its ad group's own setting,
which Google allows only when the campaign has none. In-market and
affinity segments are listed only for a name search. It reads only.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    campaign_id: Only this campaign's audiences. Optional; the account's
        lists are returned either way.
    start_date: First day of the clicks and cost (YYYY-MM-DD). Optional;
        with end_date. Default: the last 30 days.
    end_date: Last day of the clicks and cost (YYYY-MM-DD). Optional.
    segments: IN_MARKET or AFFINITY, to search Google's segment
        catalogue by name (with name_contains). Optional.
    name_contains: Text the segment names contain, e.g. "travel"
        (2 to 60 letters, digits, spaces or & , -); at most 50 segments
        come back. Required with segments.

Returns:
    Dictionary with user_lists, custom_audiences, combined_audiences,
    campaigns (audience_mode, level, audiences with metrics and, at ad
    group level, the ad group's audience_mode), segments when searched,
    date_range and notes.

Tools revision: d80f65c0.

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": {
      "customer_id": "<customer_id>"
    },
    "name": "list_audiences"
  }
}

Input Schema

Name	Required	Description	Default
`end_date`	No
`segments`	No
`start_date`	No
`campaign_id`	No
`customer_id`	Yes
`name_contains`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Reinforces rather than contradicts the readOnly/idempotent/non-destructive annotations with 'It reads only.' Adds behavior beyond the annotations that matters for interpretation: segments are returned only on a name search, at most 50 segments come back, and an ad group's audience_mode is populated only when the campaign has none (a Google-side constraint).

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

Conciseness4/5

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

Purpose is front-loaded, then structured Args/Returns blocks make scanning easy; each clause carries information about scope, defaults, or constraints. The middle paragraph is dense with detail but every element (eligibility flags, match rate, metrics, level rules) is load-bearing rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter reporting tool, the definition covers invocation constraints, defaults, segment-search behavior, and the shape of the result. Although an output schema exists, the Returns block usefully names the top-level keys so an agent can plan on them without inspecting the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates: customer_id must be numbers only with no hyphens, dates use YYYY-MM-DD with a last-30-days default, segments is IN_MARKET or AFFINITY requiring name_contains, and name_contains is constrained to 2-60 letters/digits/spaces or '& , -'. Every one of the six parameters gains meaning the schema does not supply.

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?

Opens with a specific verb+resource+scope: 'Lists the account's audiences and where its campaigns use them,' and the title anchors it to Google Ads, distinguishing it from ga4_list_audiences. The detailed enumeration of list types and campaign/ad-group attachment levels removes any ambiguity about what lands in the response.

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?

Gives concrete usage conditions: campaign_id narrows to one campaign but account lists return either way, date range defaults to the last 30 days, and in-market/affinity segments appear only when searching by name with name_contains required. It does not explicitly name the GA4 audience sibling as the alternative for cross-platform queries, so it stops short of full routing guidance.

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

All AdCopilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?