Skip to main content
Glama

campaign_bid_strategy_preview

Read-onlyIdempotent

Preview MANUAL_CPT or eligible App Store Search Results MAX_CONVERSIONS strategy.

Instructions

Preview MANUAL_CPT or eligible App Store Search Results MAX_CONVERSIONS strategy.

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>",
      "campaignId": "<campaignId>",
      "strategy": "<strategy>"
    },
    "name": "campaign_bid_strategy_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYeslocal Apple Ads profile name
strategyYes
campaignIdYes
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 / strategy / 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"
      -          ]
      -        }
      -      }
      -    }
      -  }
      -]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 / strategy / 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 / strategy / 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]+)?)$"
    • addedInput schema / properties / strategy / required
      Added value: +[
      +  "bidStrategyType",
      +  "bidStrategyGoal"
      +]
  2. First observedv0.1.0

TDQS

C2.7/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 structurally, and an output schema exists so return shape needn't be described. The description does add one piece of unstated-by-schema context: MAX_CONVERSIONS is only valid for 'eligible App Store Search Results' campaigns. It says nothing about whether preview performs validation, reports errors, or applies nothing to the live account.

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?

One sentence, front-loaded with the verb and the eligible strategy values, with no filler. It is efficient but arguably under-specified rather than genuinely concise, which keeps it off a 5.

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 four required parameters, a nested strategy object with conditional bid requirements, and an output schema, a single sentence is not enough. The agent is missing when to select this preview versus campaign_create_preview/campaign_update_preview, and how to populate the strategy object beyond the two type names.

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

Parameters2/5

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

Schema description coverage is only 50%, so the description is expected to compensate, yet it adds no meaning for profile, adAccountId, campaignId, or the nested strategy object. Critically, it does not surface the schema's conditional rule that a bid (TargetCpa) is required for MAX_CONVERSIONS and forbidden for MANUAL_CPT, which is the single most error-prone part of the call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (campaign bid strategy) and the verb (preview), and enumerates the two supported strategy types. However, it never says what a 'preview' actually produces (a dry-run validation? a projected performance estimate?), and it does not distinguish itself from siblings like campaign_update_preview or ad_group_bid_preview. Purpose is inferable but not sharply stated.

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 explicit when-to-use guidance, no statement of prerequisites (e.g. that the campaign must already exist and be an App Store Search Results campaign for MAX_CONVERSIONS), and no routing to a sibling alternative. The only implicit cue is the word 'eligible', which hints at a precondition without explaining it.

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