Google Ads MCP Server

create_custom_audience

Create a custom audience list in Google Ads by specifying customer ID, audience name, description, and membership duration. Use it to target specific users in your campaigns.

Instructions

Create a custom audience list

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": {
      "customerId": "<customerId>",
      "name": "<name>"
    },
    "name": "create_custom_audience"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Audience name
`customerId`	Yes	Google Ads customer ID
`description`	No	Audience description
`membershipDurationDays`	No	Membership duration in days

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Create a custom audience list' which is essentially the tool name restated. It does not mention potential side effects, required permissions, return values, or whether the operation is idempotent. This is effectively no behavioral transparency.

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?

The description is a single sentence with no fluff, which is concise and front-loaded. However, it is so minimal that it lacks structured detail, though it does not waste words. It earns its place by stating the purpose but could be more informative without losing conciseness.

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

Completeness2/5

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

Given the tool is a mutation with no annotations and no output schema, the description should explain what happens after creation, any prerequisites, or how it relates to other audience tools. It provides none of these. The complete schema mitigates some issues, but the description is inadequate for an agent to fully understand the tool's context and side effects.

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 all four parameters have descriptions in the schema. The tool description itself adds no parameter meaning, but the baseline for high schema coverage is 3. The schema clearly explains name, customerId, description, and membershipDurationDays.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (create) and resource (custom audience list). It is specific enough to indicate a creation operation, but it does not distinguish this tool from sibling tools that also create audience types like create_customer_match_list or create_lookalike_audience. Thus it meets the 'clear but no sibling differentiation' level.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as create_customer_match_list or create_lookalike_audience. There are no prerequisites, context, or exclusions mentioned, leaving the agent without direction on selecting this tool.

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

Deploy Server