Skip to main content
Glama

Google Ads: Set bidding strategy

ads_set_bidding_strategy
DestructiveIdempotent

Change a campaign's bidding strategy: Maximize conversions (optional target CPA), Maximize conversion value (optional target ROAS), Maximize clicks (optional max CPC), or Manual CPC. Money in real currency. Warns when a target is set with too few conversions to learn from. Previews unless confirm is 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": {
      "customer_id": "<customer_id>",
      "campaign_id": "<campaign_id>",
      "strategy": "<strategy>"
    },
    "name": "ads_set_bidding_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
strategyYes
campaign_idYes
customer_idYes
target_roasNoWith MAXIMIZE_CONVERSION_VALUE, e.g. 4 for 400%
target_cpa_majorNoWith MAXIMIZE_CONVERSIONS, e.g. 60 for a $60 target cost per lead
cpc_bid_ceiling_majorNoWith MAXIMIZE_CLICKS, the most to pay per click, e.g. 8

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm / description
      Added value: +"Leave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that: money is in real currency (major units), a warning fires when a target is set with too few conversions, and nothing changes unless confirm is true. It does not say what happens to the prior strategy settings, keeping it at 4.

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?

Three tight sentences, front-loaded with the core action, then the options, then the critical preview/warning caveats. Every sentence earns its place with no redundancy.

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 7-parameter mutation with no output schema, the description covers the essentials an agent needs: the valid strategies, currency interpretation, the confirm-to-apply contract, and the low-conversion warning. The two undocumented required IDs (customer_id, campaign_id) are self-evident from the sibling ecosystem.

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

Parameters4/5

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

At 57% schema coverage the description compensates by mapping each strategy enum value to its optional target parameter (Maximize conversions→target CPA, Maximize conversion value→target ROAS, Maximize clicks→max CPC) and clarifying that monetary values are real currency, which sharpens the *_major and target_roas semantics.

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?

States a specific verb (change/set) and resource (a campaign's bidding strategy), then enumerates the four concrete strategies with their optional targets. An agent can immediately distinguish it from siblings like ads_campaign_bidding (read) and ads_set_campaign_budget (different resource).

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?

Gives clear operational context via the preview/confirm workflow ("Previews unless confirm is true") and flags the low-conversion warning condition. It does not explicitly name alternatives such as ads_campaign_bidding or state when-not to use this tool, so it stops short of a 5.

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.