Skip to main content
Glama

ad_group_create_preview

Read-onlyIdempotent

Preview creation of one ad group.

Instructions

Preview creation of one ad group.

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": {
      "profile": "<profile>",
      "adAccountId": "<adAccountId>",
      "payload": "<payload>"
    },
    "name": "ad_group_create_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYestyped create payload for the resource
profileYeslocal Apple Ads profile name
adAccountIdYesApple Ads ad account ID

Output Schema

NameRequiredDescriptionDefault
errorNo
previewNo
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.8
    • changedInput schema / properties / payload / properties / bidStrategy / allOf
      Previous value: -[
      -  {
      -    "if": {
      -      "properties": {
      -        "bidStrategyType": {
      -          "enum": [
      -            "MANUAL_CPT"
      -          ]
      -        }
      -      },
      -      "required": [
      -        "bidStrategyType"
      -      ]
      -    },
      -    "then": {
      -      "properties": {
      -        "bidStrategyGoal": {
      -          "enum": [
      -            "TAP"
      -          ]
      -        }
      -      }
      -    }
      -  },
      -  {
      -    "if": {
      -      "properties": {
      -        "bidStrategyType": {
      -          "enum": [
      -            "MAX_CONVERSIONS"
      -          ]
      -        }
      -      },
      -      "required": [
      -        "bidStrategyType"
      -      ]
      -    },
      -    "then": {
      -      "properties": {
      -        "bidStrategyGoal": {
      -          "enum": [
      -            "INSTALL"
      -          ]
      -        }
      -      }
      -    }
      -  },
      -  {
      -    "if": {
      -      "properties": {
      -        "bidStrategyType": {
      -          "enum": [
      -            "MANUAL_CPT"
      -          ]
      -        }
      -      }
      -    },
      -    "then": {
      -      "required": [
      -        "bid"
      -      ]
      -    }
      -  }
      -]New value: +[
      +  {
      +    "if": {
      +      "properties": {
      +        "bidStrategyType": {
      +          "enum": [
      +            "MANUAL_CPT"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "bidStrategyType"
      +      ]
      +    },
      +    "then": {
      +      "properties": {
      +        "bidStrategyGoal": {
      +          "enum": [
      +            "TAP"
      +          ]
      +        }
      +      }
      +    }
      +  },
      +  {
      +    "if": {
      +      "properties": {
      +        "bidStrategyType": {
      +          "enum": [
      +            "MAX_CONVERSIONS"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "bidStrategyType"
      +      ]
      +    },
      +    "then": {
      +      "properties": {
      +        "bidStrategyGoal": {
      +          "enum": [
      +            "INSTALL"
      +          ]
      +        }
      +      }
      +    }
      +  },
      +  {
      +    "if": {
      +      "properties": {
      +        "bidStrategyType": {
      +          "enum": [
      +            "MANUAL_CPT"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "bidStrategyType"
      +      ]
      +    },
      +    "then": {
      +      "required": [
      +        "bid"
      +      ]
      +    }
      +  }
      +]
    • changedInput schema / properties / payload / properties / bidStrategy / properties / bid / description
      Previous value: -"bid or automated ceiling in account currency; auto-bidding ad group updates require zero"New value: +"campaign TargetCpa for MAX_CONVERSIONS or ad-group bid in account currency; auto-bidding ad group updates require zero"
    • changedInput schema / properties / payload / properties / bidStrategy / properties / bid / properties / amount / pattern
      Previous value: -"^(0|[1-9][0-9]*)(\\.[0-9]+)?$"New value: +"^(0\\.0*[1-9][0-9]*|[1-9][0-9]*(\\.[0-9]+)?)$"
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond the name — it does not state that no state is persisted, what the preview returns, or how it feeds into apply/verify.

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?

A single front-loaded sentence with no wasted words. Its terseness is a completeness problem, not a conciseness problem.

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

Completeness2/5

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

For a tool with a large nested create payload in a suite containing many *_preview and operations_apply siblings, the description omits the preview→apply workflow, whether changes persist, and how many ad groups can be created. The output schema helps, but the description leaves an agent guessing about the workflow.

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 the deeply nested payload, profile and adAccountId parameters are fully documented in the schema. The description contributes no additional parameter meaning, which is acceptable at baseline 3.

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 ('Preview creation of one ad group'), which distinguishes it from siblings like ad_group_update_preview or ad_group_targeting_preview. It does not, however, explain the scope or what a 'preview' produces, so differentiation is only partial.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus ad_group_update_preview, campaign_create_preview, or the apply path (operations_apply). No prerequisites or exclusions are stated.

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