AdCopilot

Google Ads: list portfolio bid strategies

list_portfolio_bidding_strategies

Read-onlyIdempotent

Lists the account's portfolio bid strategies and the campaigns on each.

A portfolio bid strategy (Target CPA, Target ROAS, Maximize Conversions,
...) is shared by every campaign assigned to it, and its target applies
to all of them. Each entry has the strategy's ID, resource name, name,
type, status, target (target CPA in micros and formatted in the account's
currency, or target ROAS as a ratio and a percentage) and its enabled or
paused campaigns. It reads only.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    include_removed: Also list removed strategies. Default: False.

Returns:
    Dictionary with bidding_strategies (each with campaigns), count,
    campaigns_on_other_strategies (campaigns on a strategy this account
    does not own, e.g. a manager account's) and a note.

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

Input Schema

Name	Required	Description	Default
`customer_id`	Yes
`include_removed`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/destructive, so the bar is lower, yet the description adds genuine semantics: a portfolio strategy's target applies to every assigned campaign, targets are expressed in micros plus formatted currency or ROAS ratio plus percentage, and campaigns on strategies owned by another account (e.g. a manager account) are surfaced separately.

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 purpose and concept explanation, then Args and Returns blocks. The Returns block partially duplicates the existing output schema, which is minor redundancy, but no sentence is filler.

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

Completeness4/5

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

A simple two-parameter read tool with annotations and an output schema; the description covers the concept, formatting of targets, argument formats, and the notable edge case of externally owned strategies. The explicit Returns narrative is slightly redundant given the output schema but not harmful.

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?

Schema description coverage is 0%, so the description must carry the load: it specifies customer_id is numbers only with no hyphens and clarifies that include_removed adds removed strategies, going beyond the bare boolean default in the schema.

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?

The description names a specific verb and resource ('Lists the account's portfolio bid strategies and the campaigns on each') and describes the shape of the returned items, making it clearly distinct from create_portfolio_bidding_strategy, update_portfolio_bidding_strategy, assign_portfolio_bidding_strategy, and bidding_audit.

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

Usage Guidelines3/5

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

Usage is implied by the read-only framing and the include_removed filter, but the description never states when to prefer this over bidding_audit or search, nor does it declare exclusions or prerequisites beyond the customer ID format.

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?