Skip to main content
Glama

publish_campaign_to_google_ads

Publish a complete Search Campaign (Budget, Campaign, Geo/Language Targeting, Ad Groups, Responsive Search Ads, Keywords, and Negative Keywords) directly to Google Ads with status=PAUSED. Requires confirm=true.

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": {
      "name": "<name>",
      "dailyBudget": "<dailyBudget>",
      "finalUrl": "<finalUrl>",
      "adGroups": "<adGroups>",
      "confirm": "<confirm>"
    },
    "name": "publish_campaign_to_google_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCampaign name.
confirmYesMust be true to execute live creation in Google Ads. Always created PAUSED so no money is spent until enabled in the Google Ads UI.
adGroupsYesAd groups to create inside the campaign.
finalUrlYesLanding page URL for the Responsive Search Ads.
targetCpaNoOptional Target CPA in account currency.
customerIdNo10-digit Google Ads customer ID (optional if set in your MCP token).
countryCodeNo2-letter target country code (e.g. 'US', 'GB', 'CA').
dailyBudgetYesDaily budget in account currency (e.g., 25 for $25/day).
languageCodeNo2-letter target language code (e.g. 'en').
loginCustomerIdNoOptional 10-digit MCC login customer ID.
negativeKeywordsNoCampaign-level negative keywords.
geoTargetConstantsNoOptional array of specific Google GeoTargetConstant resource names or numeric criteria IDs (e.g. for storm ZIP codes, counties, or metro areas).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / geoTargetConstants
      Added value: +{
      +  "description": "Optional array of specific Google GeoTargetConstant resource names or numeric criteria IDs (e.g. for storm ZIP codes, counties, or metro areas).",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed16 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / adGroups
      Added value: +{
      +  "description": "Ad groups to create inside the campaign.",
      +  "items": {
      +    "properties": {
      +      "descriptions": {
      +        "description": "2 to 4 descriptions (each max 90 characters).",
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "headlines": {
      +        "description": "3 to 15 headlines (each max 30 characters).",
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "keywords": {
      +        "items": {
      +          "properties": {
      +            "matchType": {
      +              "enum": [
      +                "BROAD",
      +                "PHRASE",
      +                "EXACT"
      +              ],
      +              "type": "string"
      +            },
      +            "text": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "text"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "path1": {
      +        "description": "Optional URL path1 (max 15 chars).",
      +        "type": "string"
      +      },
      +      "path2": {
      +        "description": "Optional URL path2 (max 15 chars).",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "headlines",
      +      "descriptions",
      +      "keywords"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / confirm / default
      Removed value: -false
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to actually publish to Google Ads. If false/omitted, returns a summary asking the user to confirm. Do NOT set this to true unless the user has explicitly asked to publish/push to Google Ads."New value: +"Must be true to execute live creation in Google Ads. Always created PAUSED so no money is spent until enabled in the Google Ads UI."
    • addedInput schema / properties / countryCode
      Added value: +{
      +  "description": "2-letter target country code (e.g. 'US', 'GB', 'CA').",
      +  "type": "string"
      +}
    • addedInput schema / properties / customerId
      Added value: +{
      +  "description": "10-digit Google Ads customer ID (optional if set in your MCP token).",
      +  "type": "string"
      +}
    • addedInput schema / properties / dailyBudget
      Added value: +{
      +  "description": "Daily budget in account currency (e.g., 25 for $25/day).",
      +  "type": "number"
      +}
    • removedInput schema / properties / draftId
      Removed value: -{
      -  "description": "The draftId returned by save_campaign_draft or generate_campaign_draft.",
      -  "exclusiveMinimum": 0,
      -  "type": "integer"
      -}
    • addedInput schema / properties / finalUrl
      Added value: +{
      +  "description": "Landing page URL for the Responsive Search Ads.",
      +  "type": "string"
      +}
    • addedInput schema / properties / languageCode
      Added value: +{
      +  "description": "2-letter target language code (e.g. 'en').",
      +  "type": "string"
      +}
    • addedInput schema / properties / loginCustomerId
      Added value: +{
      +  "description": "Optional 10-digit MCC login customer ID.",
      +  "type": "string"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Campaign name.",
      +  "type": "string"
      +}
    • addedInput schema / properties / negativeKeywords
      Added value: +{
      +  "description": "Campaign-level negative keywords.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / targetCpa
      Added value: +{
      +  "description": "Optional Target CPA in account currency.",
      +  "type": "number"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "draftId"
      -]New value: +[
      +  "name",
      +  "dailyBudget",
      +  "finalUrl",
      +  "adGroups",
      +  "confirm"
      +]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well on the highest-risk facts: this is a live write to Google Ads, everything is created PAUSED, and no spend occurs until manually enabled. It does not cover failure/partial-creation semantics, idempotency (what happens if run twice with the same name), or rate limits, which are meaningful gaps for a multi-object create.

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?

Two compact sentences, front-loaded with the action and the object inventory, then the safety-relevant constraints. Nothing is repeated and every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter nested creation tool with no annotations, the description covers the essentials: what gets built, the paused default, and the confirm gate. The main omission is the return value — with no output schema, an agent does not know whether it gets back campaign/resource IDs, which matters for any follow-up call.

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%, so all 12 parameters including the nested adGroups fields are already documented in the schema. The description adds only the confirm=true requirement, which the schema also states, so there is no net meaning added beyond structured data.

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?

Names a specific verb (Publish) and resource (Search Campaign) and enumerates exactly what gets created: Budget, Campaign, Geo/Language Targeting, Ad Groups, Responsive Search Ads, Keywords, Negative Keywords. The platform is unambiguous, which separates it from the sibling publish_campaign_to_microsoft_ads without needing to name it.

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 rather than stated: the description notes the campaign lands in PAUSED so no money is spent until enabled, which hints that a separate enable step follows, and it states the confirm=true precondition. It never says when to choose this over the Microsoft Ads sibling or when to prefer other Google Ads tools like add_google_negative_keywords, leaving the routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources