Skip to main content
Glama

Meta ads: Set campaign budget

meta_set_campaign_budget
DestructiveIdempotent

Change a Meta campaign's daily budget. Give the amount in real currency (50 means $50.00/day). Call without confirm first to see the current budget and the size of the change; a Meta campaign spends within minutes, so always show that to the human before confirming. Returns the previous value — always report both.

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": {
      "campaign_id": "<campaign_id>",
      "daily_budget_major": "<daily_budget_major>"
    },
    "name": "meta_set_campaign_budget"
  }
}

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.
campaign_idYes
daily_budget_majorYes
acknowledge_large_changeNoRequired to raise a budget by more than 50% in one step.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / confirm / default
      Added value: +false
    • 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.3/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 openWorldHint=true, so the safety profile is covered. The description adds genuinely new context: confirm=false changes nothing, budgets spend within minutes (why speed matters), and the tool returns the previous value. It stops short of permissions/auth requirements.

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?

Four short sentences, front-loaded with the action, then currency, then workflow, then return value. Each sentence carries a distinct obligation (units, preview, human approval, reporting the old value), with only minor redundancy in the approval sentence.

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?

For a destructive mutation with rich annotations and no output schema, the description covers the critical gaps: unit interpretation, the preview/confirm flow, the urgency rationale, and the return value (needed precisely because there is no output schema). Only error handling and permission requirements are unaddressed.

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 50%: confirm and acknowledge_large_change are documented in the schema, but campaign_id and daily_budget_major are not. The description compensates by explaining the unit for daily_budget_major ('50 means $50.00/day') and reinforcing the preview semantics of confirm, which is the key ambiguity an agent would otherwise get wrong.

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+resource ('Change a Meta campaign's daily budget'), and naming 'Meta' distinguishes it from the Google-side sibling ads_set_campaign_budget and from meta_set_campaign_status / meta_create_campaign. An agent can identify the operation 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 Guidelines4/5

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

Provides a clear two-phase workflow: call with confirm=false first to preview the current budget and the magnitude of the change, and only confirm after showing the human. That is strong when-to-use guidance, though it stops short of naming alternatives or conditions under which not to call it at all.

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.