Caybl

Change a Microsoft Advertising campaign's bid strategy

msads_set_bidding_strategy

DestructiveIdempotent

Switch a campaign between MaxClicks, MaxConversions, EnhancedCpc and ManualCpc. This changes how every bid is set, so it affects spend and delivery, and Microsoft re-learns after a change. Read the campaign first (msads_get_campaigns shows the current strategy). MaxConversions needs an active conversion goal (refused without one) and about 15+ conversions in the last 30 days (refused below that unless acknowledgeLowConversionVolume is true, which should only be set when the user has seen the count and still wants it). Optional targetCpa applies to MaxConversions only (Microsoft no longer offers a separate Target CPA strategy). A campaign's existing max CPC cap is kept when moving between MaxClicks and MaxConversions; Microsoft cannot add a cap back once removed, so removing it needs removeMaxCpc. Returns the previous strategy so it can be undone. Use dryRun first.

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

Input Schema

Name	Required	Description
`dryRun`	No	Preview only. Microsoft has no validate-only mode, so Caybl reads the current value and shows exactly what would change (before and after) without sending anything. Free, and cannot affect spend.
`strategy`	Yes	The strategy to switch to.
`accountId`	No	Microsoft Advertising account id or account number (e.g. 'F123ABCD'), as listed by msads_list_accounts. Only needed when the sign-in can reach more than one account.
`targetCpa`	No	MaxConversions only: target cost per conversion, in the account currency.
`campaignId`	Yes	Campaign id, from msads_get_campaigns.
`removeMaxCpc`	No	Drop the campaign's max CPC cap. Microsoft cannot add one back on this kind of campaign.
`acknowledgeLowConversionVolume`	No	Set true only if the user has seen the low conversion count and still wants MaxConversions.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds substantial context the annotations cannot: that all bids change, spend and delivery are affected, Microsoft re-learns after a change, and the previous strategy is returned so it can be undone. It also explains the irreversible max CPC removal and the lack of a validate-only mode. Minor gap: no mention of latency or how long re-learning takes.

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?

Dense but front-loaded with the core action and the strategy enum, then prerequisites. Most sentences earn their place, though the targetCpa/Microsoft-no-longer-offers aside and the max CPC cap interaction add length that could be tightened.

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 destructive 7-parameter mutation with no output schema, the definition covers what is needed: strategy options, failure preconditions, the undo path, the dryRun escape hatch, and the irreversible-cap caveat. Nothing material for correct invocation appears missing.

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 coverage is 100%, so baseline would be 3, but the description adds real meaning: it ties targetCpa to MaxConversions only and notes the standalone Target CPA strategy no longer exists, and it explains removeMaxCpc's one-way consequence (a cap cannot be re-added). acknowledgeLowConversionVolume gets usage conditions rather than just a definition.

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 ('Switch a campaign between...') and enumerates the four supported strategies, distinguishing it clearly from sibling bid-setting tools like msads_set_keyword_bid and msads_set_ad_group_bid which operate at other levels.

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 prerequisites and routing: read the campaign first via the named sibling msads_get_campaigns, use dryRun first, set acknowledgeLowConversionVolume only after the user has seen the conversion count. It also states refusal conditions (no conversion goal, under ~15 conversions) so the agent knows when this call will fail.

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

All Caybl 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?