AdCopilot

Google Ads: create ad group

create_ad_group

Creates a new ad group within a campaign.

A new ad group holds no ads or keywords, so on its own it shows nothing
and spends nothing; it serves only once an ad and keywords are added.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    campaign_id: The ID of the campaign to add the ad group to.
    name: The name for the new ad group.
    cpc_bid_micros: Default max CPC bid in micros of the account's currency (1000000 = 1.00: ₹1 on an INR account, $1 on a USD one). Default: 1000000.
    ad_group_type: Ad group type. One of: SEARCH_STANDARD, DISPLAY_STANDARD, SHOPPING_PRODUCT_ADS, VIDEO_BUMPER, VIDEO_TRUE_VIEW_IN_STREAM. Default: SEARCH_STANDARD.
    status: Initial status. One of: ENABLED, PAUSED. Default: ENABLED. In
        a campaign that is already running, an ENABLED ad group serves,
        from that campaign's budget, as soon as it has an approved ad and
        keywords; pass PAUSED to hold it.

Returns:
    Dictionary with the created ad group resource name.

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

Input Schema

Name	Required	Default
`name`	Yes
`status`	No	ENABLED
`campaign_id`	Yes
`customer_id`	Yes
`ad_group_type`	No	SEARCH_STANDARD
`cpc_bid_micros`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover write/non-destructive/non-idempotent/openWorld, so the description's job is added context — and it delivers: the new ad group is inert until ads and keywords exist, ENABLED status begins serving from the campaign budget immediately, and PAUSED is the safe hold. It does not warn about duplicate ad group names or what failures look like, but the lifecycle behaviour is well disclosed.

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?

Front-loaded purpose sentence, then a structured Args/Returns block with no filler. The status explanation partially restates the earlier "serves only once an ad and keywords are added" point, a minor redundancy in an otherwise tight definition.

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 6-parameter mutation tool this is complete: every parameter is described, defaults are given, enum values are enumerated, the return value shape is stated (and an output schema exists), and the serving implications of the created object are disclosed.

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?

Schema description coverage is 0%, so the description must carry all parameter meaning and it does: customer_id is digits-only without hyphens, cpc_bid_micros is explained with a concrete conversion (1000000 = 1.00) and per-currency example, and both enum lists (ad_group_type, status) are spelled out along with status defaults and consequences.

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 opening sentence uses a specific verb and resource ("Creates a new ad group within a campaign") and the second sentence scopes what the resulting object is. It is clearly distinct from create_campaign and update_ad_group, though no sibling is named explicitly, which keeps it just 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 Guidelines3/5

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

The description explains the state consequence of creating an ad group (holds no ads or keywords, spends nothing until they are added) and notes passing PAUSED to hold an ad group in a running campaign, which implicitly tells the agent when to pick one status over another. It never states prerequisites versus alternatives such as create_campaign first, or when to prefer update_ad_group.

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?