Google Ads MCP Server

create_lookalike_audience

Create a lookalike audience from a seed audience in Google Ads. Provide customer ID, seed audience ID, and name to expand targeting to similar users.

Instructions

Create a lookalike/similar audience

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>",
      "seedAudienceId": "<seedAudienceId>",
      "name": "<name>"
    },
    "name": "create_lookalike_audience"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	New audience name
`customerId`	Yes	Google Ads customer ID
`seedAudienceId`	Yes	Seed audience ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.8/5.0

Behavior2/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 behavioral disclosure. It only says 'Create a lookalike/similar audience' without mentioning required permissions, whether the seed audience must exist, what happens on invalid input, reversibility, or any side effects. This is insufficient for a mutation tool.

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 description is concise and front-loaded, consisting of one short sentence. However, it largely restates the tool name and adds little value ('lookalike/similar' is a synonym), so it does not fully earn its place as a meaningful addition.

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?

The tool is a mutation with no annotations and no output schema. The description lacks any contextual detail about prerequisites, return values, or behavior. Given the presence of many sibling audience tools, the description is not complete enough to guide an agent effectively.

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?

The input schema has 100% coverage with descriptions for each parameter ('New audience name', 'Google Ads customer ID', 'Seed audience ID'). The description adds no extra parameter meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 the resource ('lookalike/similar audience'). It is specific enough to understand the tool's purpose, but it does not explicitly differentiate from sibling tools like create_custom_audience or create_customer_match_list, so it falls short of a 5.

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. There is no mention of prerequisites, exclusions, or scenarios where a different audience creation method would be more appropriate. This is a clear gap.

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

Deploy Server