Skip to main content
Glama

Meta ads: Set ad set budget

meta_set_ad_set_budget
DestructiveIdempotent

Change a Meta ad set's daily budget, in real currency (30 means $30.00/day). Call without confirm first to see the current budget and the size of the change. Raising it more than 50% at once needs acknowledge_large_change. For a budget set on the campaign, use meta_set_campaign_budget.

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": {
      "adset_id": "<adset_id>",
      "daily_budget_major": "<daily_budget_major>"
    },
    "name": "meta_set_ad_set_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.
adset_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. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already mark this as destructive, non-read-only, idempotent, and open-world. The description adds meaningful behavior beyond that: a preview-first workflow, the current-budget/change-size preview, and the large-change guard threshold. It does not discuss permissions or rate limits, but the key mutation-safety behavior is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences with zero waste: purpose first, operational preview/threshold guidance second, and sibling redirection third. The information is front-loaded and easy for an agent to act on.

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 budget mutation with no output schema, the description provides the critical context: preview-before-confirm, currency semantics, large-change acknowledgment, and the campaign-budget alternative. It is nearly complete, though it could say slightly more about what the preview output contains or how adset_id is obtained.

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 50%, so the description must compensate for some parameters. It clarifies daily_budget_major uses real currency with a concrete example, reinforces the preview meaning of confirm, and explains the >50% condition for acknowledge_large_change. adset_id remains undocumented, but its meaning is largely self-evident.

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: change a Meta ad set's daily budget. It also clarifies the currency unit and distinguishes the sibling campaign-budget tool, so an agent can identify the correct operation without opening schemas.

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?

Explicitly says to call without confirm first to preview, explains that acknowledge_large_change is required for raises over 50%, and names meta_set_campaign_budget for campaign-level budgets. These are concrete when/when-not and alternative-selection instructions.

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.