Adsap

Add Ad Group to Google Campaign

adsap_google_create_ad_group

Add an ad group to an EXISTING Google Ads campaign (Search, Display or Demand Gen) in ONE atomic request: the ad group, optional keywords (Search only) and optionally one ad. This is the only tool that adds structure to an already-created campaign — the create-campaign tools always build a fresh campaign. Declare channel to match the campaign's type (SEARCH -> 'search', DISPLAY -> 'display', DEMAND_GEN -> 'demand_gen' — from adsap_google_list_campaigns); the workflow verifies the campaign exists and rejects mismatches (PMax uses asset groups and is NOT supported; App/Shopping ad groups are also unsupported). SAFETY: if the parent campaign is ACTIVE the new ad group is created PAUSED by default so it never starts spending unreviewed — pass ad_group.status 'ENABLED' to override; if the campaign is PAUSED the ad group is created ENABLED (the campaign gates serving). Per channel: SEARCH — ad_group.keywords [{text, match_type EXACT|PHRASE|BROAD}] (optional but the group gets no traffic without them) and an optional responsive search ad (3-15 headlines max 30 chars w/ optional pinned_field, 2-4 descriptions max 90, final_url, path1/path2). DISPLAY — optional optimized_targeting flag and an optional responsive display ad (same shape as adsap_google_create_display_campaign's ad: >=1 landscape AND >=1 square image asset id, 1-5 headlines, exactly 1 long_headline, 1-5 descriptions, business_name, final_url). DEMAND_GEN — geo is REQUIRED at the AD GROUP level (ad_group.geo.location_ids; unlike Search/Display where geo is campaign-level and cannot be set here), plus optional language_ids, channel controls (ad_group.channels.strategy or .selected) and an optional 'multi_asset' image ad or 'video_responsive' YouTube ad (same shapes as adsap_google_create_demand_gen_campaign). An ad group created WITHOUT an ad will not serve until an ad is added. EXISTING-GROUP MODE: pass ad_group_id INSTEAD of ad_group to add ONE responsive search ad to an ad group that already exists (Search only; ad becomes required; ad.status defaults to PAUSED — pass ENABLED to create it serving; the workflow verifies the group exists, is not removed, and belongs to campaign_id). Use dry_run: true first — Google validates the whole chain without creating anything. ad_account_id is the bare 10-digit customer ID.

Input Schema

TableJSON Schema

Name	Required	Description
`ad`	No	Optional — omit to create the ad group without an ad (it will not serve until one is added).
`channel`	Yes	Must match the campaign's advertising channel type. The workflow verifies and rejects mismatches.
`dry_run`	No
`ad_group`	No	CREATE MODE: the new ad group to create. Mutually exclusive with ad_group_id — exactly one of the two is required.
`ad_group_id`	No	EXISTING-GROUP MODE: numeric id of an EXISTING ad group (from the campaign's ad group list) — the tool then ONLY creates one responsive search ad inside it (search only; `ad` required). Mutually exclusive with ad_group.
`campaign_id`	Yes	Numeric id of the EXISTING campaign to add the ad group to (from adsap_google_list_campaigns).
`ad_account_id`	Yes	Bare 10-digit Google Ads customer ID (from adsap_google_list_ad_accounts). No dashes, no act_ prefix.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and delivers extensively: atomicity, safe PAUSED defaults, ENABLED override behavior based on campaign status, the fact that a group without an ad will not serve, dry_run validation semantics, and verification that the campaign/ad group exists. This is exemplary transparency for a mutating tool.

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 long, but the length is justified by three channel variants and two operation modes. The core purpose is front-loaded in the first sentence, and the content is organized into clear labeled clusters: channel rules, SAFETY defaults, per-channel requirements, EXISTING-GROUP MODE, and dry_run. Slightly dense, but every portion earns its place.

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 highly complex tool with no output schema and no annotations, the description is remarkably complete: it covers required inputs, defaults, valid modes, unsupported campaign types, cross-parameter constraints, and safe invocation via dry_run. An agent has enough context to call the tool correctly across all supported channels.

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?

Even though schema coverage is high at 86%, the description adds substantial meaning: mutual exclusivity of ad_group vs ad_group_id, channel-specific field requirements, geo being required at ad group level for Demand Gen, keyword optionality with the warning that Search gets no traffic without them, and ad shape variants per channel. It goes well beyond the schema.

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 opens with a specific verb and resource: add an ad group to an EXISTING Google Ads campaign, and clarifies it covers Search, Display, or Demand Gen. It explicitly distinguishes itself from create-campaign tools, so an agent can immediately tell it apart from adsap_google_create_search_campaign and similar siblings.

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

Usage Guidelines5/5

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

The description states exactly when to use this tool: to add structure to an already-created campaign, and when not to: PMax, App, and Shopping are unsupported. It also names the alternative context via EXISTING-GROUP MODE and points to adsap_google_list_campaigns for IDs, leaving no ambiguity about selection.

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

All Adsap 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?