Google Ads MCP Server

create_ad_group

Create a new paused ad group within a Google Ads campaign, specifying name and optional CPC bid.

Instructions

Create a new ad group (in PAUSED state)

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>",
      "campaignId": "<campaignId>",
      "name": "<name>"
    },
    "name": "create_ad_group"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Ad group name
`campaignId`	Yes	Campaign ID
`customerId`	Yes	Google Ads customer ID
`cpcBidMicros`	No	CPC bid in micros

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses one key trait—the ad group starts in PAUSED state—but does not mention other important behaviors such as whether the ad group is immediately available, whether the operation is idempotent, or what the response contains. It is partially transparent but incomplete.

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 one concise sentence that front-loads the action and key state detail. It contains no filler or redundant information, earning a perfect score for conciseness.

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

Completeness3/5

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

Given the tool's simplicity and the schema's completeness, the description covers the core purpose and the paused-state behavior. However, it lacks guidance on the creation result (e.g., generated ad group ID) and any follow-up steps, which would make it more complete. It is adequate but not exceptional.

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 schema has 100% description coverage for all parameters, so the schema already provides the meaning. The description adds no extra parameter-level context beyond what's in the schema, which aligns with the baseline of 3.

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 clearly states the action ('Create') and resource ('new ad group'), and adds a specific detail ('in PAUSED state') that distinguishes it from other creation tools. It unambiguously identifies what the tool does relative to siblings like create_campaign or create_responsive_search_ad.

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

Usage Guidelines3/5

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

The description implies the tool is for creating ad groups, but it does not explicitly state when to use it versus alternatives, mention prerequisites (e.g., a valid campaignId), or explain the significance of the PAUSED state. No exclusions or context are provided, so it's merely implied usage.

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

Deploy Server