AdLoop: Google Ads, Reddit Ads & GA4

Overview Schema Source Related Servers Discussions Admin

Draft a Shopping campaign

draft_shopping_campaign

Draft a paused Standard Shopping campaign for a linked Merchant Center feed, returning a preview with budget, ad group, Shopping ad, and product group before applying.

Instructions

Draft a Standard Shopping campaign that advertises a Merchant Center feed — returns a PREVIEW.

Creates the budget, the campaign (PAUSED), a product ad group with its Shopping ad, and one "All products" product group, in one atomic request. The Merchant Center account must be linked to the Google Ads account; the draft checks that. Shopping campaigns take no keywords and no language targeting (the feed's language applies). Nothing changes until confirm_and_apply applies the plan_id; a dry run has Google validate it.

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

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": {
      "campaign_name": "<campaign_name>",
      "daily_budget": "<daily_budget>",
      "merchant_id": "<merchant_id>",
      "product_bid": "<product_bid>",
      "geo_target_ids": "<geo_target_ids>"
    },
    "name": "draft_shopping_campaign"
  }
}

Input Schema

Name	Required	Description	Default
`max_cpc`	No	Optional CPC ceiling for TARGET_SPEND, in account currency.
`feed_label`	No	Optional feed label to limit the campaign to one feed of the Merchant Center account.
`customer_id`	No	Google Ads customer ID (digits, dashes optional). Defaults to the configured account.
`merchant_id`	Yes	Numeric Merchant Center id (from list_merchant_accounts) whose products the campaign advertises.
`product_bid`	Yes	CPC bid of the "All products" group in account currency. Google requires it even when the bid strategy sets bids.
`target_roas`	No	Target return on ad spend for TARGET_ROAS, e.g. 4.0 for 400%.
`daily_budget`	Yes	Daily budget in account currency, checked against the max_daily_budget safety cap.
`ad_group_name`	No	Optional ad group name; defaults to "<campaign> - All products".
`campaign_name`	Yes	Name of the new campaign.
`geo_target_ids`	Yes	Countries or regions as geo target constant ids, e.g. ["2276"] for Germany. Required.
`bidding_strategy`	No	MANUAL_CPC (default), TARGET_SPEND (Maximize clicks) or TARGET_ROAS.	MANUAL_CPC
`campaign_priority`	No	LOW (default), MEDIUM or HIGH. With several Shopping campaigns on the same products, the higher priority serves first.	LOW
`search_partners_enabled`	No	Also serve on Google search partners.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.27.1Oct 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description goes well beyond them: it discloses the atomicity of the request, that the campaign is created PAUSED, that the result is a preview/draft that changes nothing until confirm_and_apply, and that a dry run has Google validate it. That is exactly the behavioral context an agent needs for a multi-entity create tool.

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?

Purpose and PREVIEW nature are front-loaded in the first sentence, followed by a compact block covering what is created, the prerequisite, the Shopping-specific constraints, and the confirm step. No sentence is filler; the API doc link is the only extra.

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 13-parameter, output-schema-backed draft tool, the definition covers everything an agent must know before calling: the required Merchant Center link, the PAUSED draft state, atomic creation of all sub-entities, and the confirm_and_apply handoff. Return-value detail is unnecessary because an output schema exists.

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?

Schema description coverage is 100% across 13 parameters, so the schema already carries per-parameter meaning (defaults, currency, enum-like strategy values). The description adds little parameter-level detail beyond noting the feed and the mandatory 'All products' group bid, so this sits at the baseline for a fully documented 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 names a specific verb+resource+scope: 'Draft a Standard Shopping campaign that advertises a Merchant Center feed — returns a PREVIEW.' The Shopping-specific detail plus the enumeration of what gets created (budget, PAUSED campaign, product ad group, Shopping ad, 'All products' product group) clearly separates it from draft_campaign, draft_pmax_product_exclusions, and the Reddit draft siblings.

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

Usage Guidelines4/5

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

Strong on prerequisites and constraints ('Merchant Center account must be linked', 'no keywords and no language targeting') and it names the follow-up path ('Nothing changes until confirm_and_apply applies the plan_id'). It does not explicitly say when to prefer this over the generic draft_campaign or draft_pmax siblings, so routing guidance is implied by campaign type rather than stated.

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

Deploy Server