Google Ads MCP Server

create_demand_gen_campaign

Create a Demand Gen campaign in Google Ads by specifying customer ID, name, daily budget, and target audience. This tool configures campaigns for Discovery, YouTube In-Feed, and Gmail placements.

Instructions

Create a Demand Gen campaign

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>",
      "budgetAmountMicros": "<budgetAmountMicros>"
    },
    "name": "create_demand_gen_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Campaign name
`customerId`	Yes	Google Ads customer ID
`targetAudience`	No
`budgetAmountMicros`	Yes	Daily budget in micros

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.2/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 states 'Create' which implies mutation, but does not mention permissions required, side effects, or return behavior. This is minimal and insufficient for a create operation.

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 a single, front-loaded sentence that is extremely concise and free of filler. Every word earns its place, making it easily parseable.

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 campaign creation operation with no output schema and no annotations, and the description is too terse to cover the behavioral or contextual aspects. Given the complexity of Google Ads campaign types, this description is incomplete for an agent to use confidently.

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 covers 75% of parameters with descriptions, so most parameter meanings are available. However, the description adds no additional parameter context beyond what the schema already provides, and the 'targetAudience' enum lacks description in both schema and tool 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 uses a specific verb 'Create' and identifies a distinct resource type 'Demand Gen campaign', clearly distinguishing it from sibling tools like 'create_campaign' or 'create_performance_max_campaign'. This provides immediate clarity on the tool's function.

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 gives no guidance on when to use Demand Gen campaigns versus other campaign types. It does not mention any prerequisites, exclusions, or alternative tools, leaving the agent to infer usage context from the tool name alone.

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

Deploy Server