AdCopilot

Google Ads: change portfolio bid strategy target

update_portfolio_bidding_strategy

DestructiveIdempotent

Changes a portfolio bid strategy's target or name.

The new target applies to every campaign on the strategy; the result
says how many, and gives the target before and after formatted in the
account's currency. target_cpa_micros applies to a TARGET_CPA or
MAXIMIZE_CONVERSIONS portfolio, target_roas to a TARGET_ROAS or
MAXIMIZE_CONVERSION_VALUE one; any other combination is refused before
anything is sent. The target of a campaign's own (standard) strategy is
changed with update_campaign.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    bidding_strategy_id: The portfolio strategy's ID, or its resource
        name (customers/<customer_id>/biddingStrategies/<id>).
    target_cpa_micros: New target cost per conversion in micros of the
        account's currency (10000000 = 10.00: ₹10 on an INR account, $10
        on a USD one). Optional.
    target_roas: New target return on ad spend as a ratio (4.0 for 400%),
        from 0.01 to 1000. Optional.
    name: New name, distinct within the account. Optional.

Returns:
    Dictionary with bidding_strategy_resource_name, before and after
    (target and name), campaigns_affected and a message.

Tools revision: d80f65c0.

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>",
      "bidding_strategy_id": "<bidding_strategy_id>"
    },
    "name": "update_portfolio_bidding_strategy"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`customer_id`	Yes
`target_roas`	No
`target_cpa_micros`	No
`bidding_strategy_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.7/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; the description adds real context on top, namely the blast radius (the new target applies to every campaign on the strategy), pre-flight validation that refuses bad combinations before anything is sent, and that before/after targets come back in the account's currency. It stops short of naming required permissions or whether the change can be reverted, so it is strong but not exhaustive.

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?

Front-loaded with the one-line purpose, then constraint rules, then Args and Returns blocks; almost every sentence adds information. It is somewhat longer than strictly necessary, and the Returns block partly duplicates the output schema, but nothing is padding.

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 five-parameter destructive mutation, the definition covers purpose, valid parameter combinations, currency/micros semantics, blast radius, and return contents. An agent has everything needed to decide to call it and to construct a valid call.

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

Parameters5/5

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

With 0% schema description coverage the description must carry the load, and it does: customer_id format (numbers only, no hyphens), bidding_strategy_id accepting either a bare ID or a full resource name, micros conversion with a concrete INR/USD example, target_roas as a ratio with a 0.01-1000 range, and name uniqueness within the account.

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 and resource ('Changes a portfolio bid strategy's target or name') and explicitly separates the portfolio case from the standard-strategy case handled by update_campaign, so an agent can distinguish it from siblings without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit applicability rules: target_cpa_micros only for TARGET_CPA or MAXIMIZE_CONVERSIONS, target_roas only for TARGET_ROAS or MAXIMIZE_CONVERSION_VALUE, with invalid combinations refused. It also routes the standard-strategy case to update_campaign, covering both when-to-use and when-not-to-use.

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

All AdCopilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?