AdCopilot

Google Ads: create ad group

create_ad_group

Creates a new ad group within a campaign.

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: 5c9bea8f.

Input Schema

TableJSON 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

TableJSON 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 declare this is a non-read-only, non-idempotent, non-destructive mutation, so the description does not need to restate those basics. It adds meaningful behavioral context: cpc_bid_micros currency semantics, allowed ad group types, and what an ENABLED ad group does in an already-running campaign.

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 front-loaded, clearly structured under Args and Returns, and every section is relevant. It repeats a few schema defaults, but those repetitions support interpretation of currency and enum meaning rather than adding noise.

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?

An output schema exists, so the description does not need to explain return values in depth, and it still briefly notes that the return includes the created resource name. Combined with full parameter documentation and status semantics, it gives an agent enough information to invoke this creation tool correctly.

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 the full parameter burden, and it does: it documents all six parameters, including customer ID formatting, campaign ID purpose, cpc bid micros conversion, ad_group_type enum values, and status enum values and defaults.

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 states a specific verb and resource: creates a new ad group within a campaign. That is much clearer than a tautology, but it does not explicitly distinguish this from the sibling update_ad_group or create_campaign tools.

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?

Usage is implied by 'Creates a new ad group within a campaign,' and the status parameter includes useful operational guidance about ENABLED versus PAUSED. However, it does not explicitly say when to use this instead of update_ad_group or how to choose the parent campaign in context.

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?