Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Draft an ad group

draft_ad_group

Generate a preview for a new SEARCH ad group in an existing campaign, optionally adding keywords; nothing changes until you confirm and apply.

Instructions

Draft a new ad group within an existing campaign — returns a PREVIEW, does NOT create.

Creates an ad group (ENABLED, type SEARCH_STANDARD) in the specified campaign, optionally with keywords in the same atomic operation. Only SEARCH campaigns are supported. Ads are not included, so the ad group cannot serve until one of its ads is created and enabled.

Returns a preview with a plan_id plus warnings (BROAD keywords on a non-Smart-Bidding campaign, a duplicate ad group name, a CPC bid that Smart Bidding ignores); nothing changes until confirm_and_apply applies it.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsNoOptional list of {"text": "keyword", "match_type": "EXACT|PHRASE|BROAD"}.
campaign_idYesThe campaign to add the ad group to (numeric ID as returned by get_campaign_performance).
customer_idNoGoogle Ads customer ID (digits, e.g. "1234567890"). Empty uses the configured default account.
ad_group_nameYesName for the new ad group.
cpc_bid_microsNoOptional ad group CPC bid in micros (1,000,000 = one unit of the account's currency); only used by MANUAL_CPC campaigns. 0 means no ad-group bid; must not be negative.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.27.1
    • addedInput schema / properties / ad_group_name / description
      Added value: +"Name for the new ad group."
    • addedInput schema / properties / campaign_id / description
      Added value: +"The campaign to add the ad group to (numeric ID as returned\nby get_campaign_performance)."
    • addedInput schema / properties / cpc_bid_micros / description
      Added value: +"Optional ad group CPC bid in micros (1,000,000 = one\nunit of the account's currency); only used by MANUAL_CPC campaigns.\n0 means no ad-group bid; must not be negative."
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID (digits, e.g. \"1234567890\"). Empty\nuses the configured default account."
    • addedInput schema / properties / keywords / description
      Added value: +"Optional list of {\"text\": \"keyword\", \"match_type\":\n\"EXACT|PHRASE|BROAD\"}."
  2. First observedv0.9.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare non-readonly, non-destructive, open-world, but the description goes further: it specifies what gets created (ENABLED, SEARCH_STANDARD), that keywords can be added atomically, that ads are omitted so it can't serve, and that a plan_id plus warnings (BROAD keywords, duplicate names, ignored CPC bid) are returned with no side effects until applied. This is rich behavioral context beyond annotations.

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 with the key 'PREVIEW, does NOT create' distinction in the first line, followed by tightly organized behavior details. The trailing API documentation URL is somewhat expendable, keeping it just short of a 5.

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?

With an output schema covering the return (plan_id, warnings) and annotations covering the safety profile, the description fills the remaining gaps: scope limits (SEARCH only), atomicity, and the confirm workflow. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it explains the atomic keyword creation, the CPC-bid-ignored-by-Smart-Bidding warning, and the duplicate-name warning context. It does not fully restate the micros/customer_id semantics already in the schema, but the warning behavior adds value.

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?

States a specific verb+resource ('Draft a new ad group within an existing campaign') and immediately disambiguates with 'returns a PREVIEW, does NOT create.' An agent can distinguish this from sibling mutation tools like draft_campaign, draft_keywords, and confirm_and_apply without opening the schema.

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?

Explicit about scope ('Only SEARCH campaigns are supported'), preconditions (campaign must exist, ads needed before serving), and the workflow boundary ('nothing changes until confirm_and_apply applies it'). The when-to-use and the alternative (confirm_and_apply) are both named.

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

Deploy Server

Other Tools