Skip to main content
Glama

Update a Meta campaign

ads_update_campaign
Idempotent

Rename a Meta campaign, change its Advantage campaign budget (whole currency units, same daily or lifetime type it has) or bid strategy, or set or remove its spend cap (null removes it; Meta's minimum is about 100 USD). Campaigns that budget per ad set take budget and bid changes on the ad set (ads_update_ad_group). Raising a budget on an active campaign spends more real money: confirm the new amount with the user first. Meta changes are paced and limited so the ad account does not look automated: on ads_change_limited, wait retryAfterSeconds before retrying; on confirmation_required, confirm the new budget with the user and retry with confirmLargeChange 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": {
      "adAccountId": "<adAccountId>",
      "campaignId": "<campaignId>"
    },
    "name": "ads_update_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
budgetNo
platformNometa_ads, tiktok_ads or linkedin_ads. Needed only when the profile has more than one ad network and no accountId is given.
spendCapNo
accountIdNoThe Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection.
profileIdNoA profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree.
campaignIdYesA campaign id from ads_get_tree.
adAccountIdYes
bidStrategyNo
confirmLargeChangeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmLargeChange
      Added value: +{
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), the description discloses that budget amounts are whole currency units, that null removes the spend cap, Meta's ~100 USD minimum, and that a budget increase spends real money on an active campaign. It also explains the external pacing/limiting behavior and the ads_change_limited / confirmation_required responses with the retryAfterSeconds and confirmLargeChange recovery paths.

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?

It is a single dense paragraph with zero filler and front-loads the operations before the warnings. The error-handling tail is somewhat compressed, but every sentence carries operational information.

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 10-parameter mutation tool with no output schema and open-world behavior, it covers the money-risk warning, the sibling routing for per-ad-set budgets, and the retry protocol for external throttling and confirmation gating. Nothing an agent needs to call it correctly is 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 only 40%, and the description compensates for the highest-risk fields: budget must keep the same daily/lifetime type, amounts are whole currency units, spendCap null semantics and the minimum, and the meaning of confirmLargeChange. It adds nothing for bidStrategy's four enum values or for platform/accountId/profileId/campaignId, though those carry schema descriptions.

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 the resource (a Meta campaign) and enumerates the exact operations: rename, change Advantage campaign budget or bid strategy, set/remove spend cap. It also explicitly carves out per-ad-set-budget campaigns and names the sibling that handles them (ads_update_ad_group), so an agent can distinguish it from siblings without opening a 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?

It states when to use this tool versus ads_update_ad_group ('Campaigns that budget per ad set take budget and bid changes on the ad set'), and gives an explicit pre-call rule: confirm a raised budget with the user before applying it. It also gives conditional retry guidance keyed to two error responses.

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.

Resources