Skip to main content
Glama

campaign_create_preview

Read-onlyIdempotent

Preview creation of one campaign and return a ten-minute receipt.

Instructions

Preview creation of one campaign and return a ten-minute receipt.

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": "campaign_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. Changed4 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": [
      +            "MAX_CONVERSIONS"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "bidStrategyType"
      +      ]
      +    },
      +    "then": {
      +      "required": [
      +        "bid"
      +      ]
      +    }
      +  },
      +  {
      +    "if": {
      +      "properties": {
      +        "bidStrategyType": {
      +          "enum": [
      +            "MANUAL_CPT"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "bidStrategyType"
      +      ]
      +    },
      +    "then": {
      +      "not": {
      +        "required": [
      +          "bid"
      +        ]
      +      }
      +    }
      +  }
      +]
    • changedInput schema / properties / payload / properties / bidStrategy / description
      Previous value: -"required type and goal pair; manual strategies require a positive bid"New value: +"required type and goal pair; MAX_CONVERSIONS requires a positive bid (TargetCpa) and MANUAL_CPT must not include 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

B3.2/5.0
Behavior3/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 does add genuinely new behavioral context — that a ten-minute receipt is returned — but it never explains what that receipt is for or that it expires, which is the one detail an agent most needs.

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?

A single front-loaded sentence with no filler and no repetition of structured data. It is efficient but borders on under-specification given the complexity of the payload.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the input schema covers the nested payload thoroughly. What is missing is the operational context: that this is a non-mutating preview whose receipt feeds a subsequent apply call, which matters a lot in a server with this many near-identically named preview tools.

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% and the nested payload, bid strategy conditionals, and targeting structure are all documented in the schema itself. The description adds nothing about the three top-level parameters, so baseline 3 applies when the schema carries the full burden.

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?

States a specific verb and resource: previewing the creation of one campaign. It is clear what the tool does, but it does not distinguish itself from closely named siblings such as campaign_update_preview, ad_group_create_preview, or campaign_bid_strategy_preview — all of which share the same preview pattern.

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?

No guidance on when to use this versus operations_apply/operations_verify, or that the preview must be executed afterwards. The description also omits any prerequisite such as a valid profile or ad account, leaving the preview→apply workflow entirely to inference.

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