Optimize Meta Budget

User asks about Meta/Facebook/Instagram budget optimization, reallocating ad spend, maximizing conversions with their budget, or wants data-driven budget recommendations.

This tool uses linear programming (scipy.optimize) to find the optimal budget allocation across Meta Ads campaigns or ad sets to maximize conversions while respecting constraints.

Returns:

Optimal budget allocation for each campaign/ad set
Expected conversion lift from reallocation
Campaigns to scale up (high ROAS performers)
Campaigns to reduce (below target ROAS)
Campaigns to consider pausing (ROAS < 1.0)
Actionable recommendations
CBO (Campaign Budget Optimization) notes

When to use this tool:

“How should I allocate my Meta budget?”
“Optimize my Facebook ad spend for conversions”
“Which Instagram campaigns should I increase budget?”
“Reallocate my $5000 Meta budget”
“Maximize conversions with my current spend”
“What’s the optimal budget split across campaigns?”

Parameters:

total_budget: Total daily budget to allocate (required, e.g., 5000.00)
lookback_days: 7, 14, 30 (default), 60, or 90 days for analysis
start_date: Optional start date (YYYY-MM-DD). Overrides lookback_days when used with end_date.
end_date: Optional end date (YYYY-MM-DD). Overrides lookback_days when used with start_date. ⚠️ DATE CLARIFICATION: If the user’s date request is vague or ambiguous (e.g., “March to June” without a year, “last quarter”, “recently”, “a few months ago”), ask the user to specify exact dates before calling this tool. Do not assume or guess dates.
target_roas: Optional override (default: from account goals or 2.0x)
max_change_percentage: Max budget change per item (default: 0.5 = 50%)
min_daily_budget: Minimum budget per item (default: 5.00)
optimization_level: ‘campaign’ (default) or ‘ad_set’
ad_account_id: Required for multi-account users. Get from list_connected_accounts

Execution time: 2-5 seconds (cached database query + optimization) Data source: campaign_daily_metrics + ad_group_daily_metrics tables

Key concepts:

Linear Programming: Mathematical optimization to maximize objective (conversions) subject to constraints
Efficiency Score: Conversions per dollar spent - used to prioritize allocation
Max Change Constraint: Prevents dramatic shifts (e.g., ±50% max from current)
Target ROAS: 3-tier resolution: account_goals - 90-day historical - default 2.0x

Meta-specific considerations:

CBO campaigns: Budget set at campaign level, Meta distributes to ad sets
ABO campaigns: Budget set at ad set level, more granular control
Learning Phase: New campaigns need 50+ conversions before optimization

POST

api

tools

optimize_meta_budget

execute

Optimize Meta Budget

curl --request POST \
  --url https://api.adspirer.ai/api/v1/tools/optimize_meta_budget/execute \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "arguments": {
    "date_range": "string",
    "end_date": "string",
    "lookback_days": 30,
    "raw_data": false,
    "start_date": "string",
    "target_roas": 1,
    "total_budget": 1
  }
}
'

{
  "data": {
    "quota": {
      "limit": 150,
      "period_end": "2026-05-01",
      "tier": "plus",
      "used": 42
    },
    "text": "(tool-specific textual output for optimize_meta_budget)"
  },
  "success": true,
  "tool": "optimize_meta_budget"
}

Authorizations

Authorization

string

header

required

API key from https://adspirer.ai/keys. Prefix sk_live_. Treat as a secret — never commit.

Headers

Idempotency-Key

string<uuid>

Client-generated UUID to make writes idempotent. Strongly recommended for write tools. A repeat call with the same key returns the cached result instead of re-executing. Example: 550e8400-e29b-41d4-a716-446655440000

Body

application/json

All tool arguments are wrapped in an arguments object. The fields accepted inside arguments are listed below — required fields are marked with a red asterisk.

arguments

object

required

Input schema for Meta budget allocation optimization

Show child attributes

Response

Tool executed successfully. data.text carries the human-readable result (markdown-friendly). data.quota shows your current usage against the plan limit. data.structured appears when the tool emits machine-parseable structured content. data.content appears for tools that return non-text blocks (images, resources).

Returned on HTTP 200. data.text is the primary human-readable output. data.quota is always present for billable calls. data.structured is set only when the tool emits machine-parseable structured content. data.content is set only when the tool emits non-text content blocks.

data

object

required

Show child attributes

success

boolean

required

tool

string

required

Echoed tool_name from the request URL.

Last modified on April 23, 2026

Optimize Meta PlacementsUser asks about Meta/Facebook/Instagram placement performance, which placements work best, Feed vs Stories vs Reels, should they use Audience Network, or wants placement optimization recommendations. This tool analyzes placement-level performance (Feed, Stories, Reels, Audience Network, Messenger, etc.) and provides optimization recommendations including budget reallocation suggestions. Returns: - Placement ROAS ranking (sorted by performance) - Placements categorized as SCALE/MAINTAIN/REDUCE/EXCLUDE - Budget reallocation recommendations between placements - Expected ROAS improvement from optimization - Optimal placement mix for campaign objective - Savings from excluding underperforming placements - Actionable recommendations and quick actions When to use this tool: - "Which Meta placements should I use?" - "Should I exclude Audience Network?" - "Instagram Stories vs Reels - which is better?" - "Feed vs Stories performance comparison" - "Where should I allocate my Meta ad budget?" - "Which placements are wasting money?" - "What's the optimal placement mix for conversions?" - "Facebook Marketplace performance?" Parameters: - lookback_days: 7, 14, 30 (default), 60, or 90 days - start_date: Optional start date (YYYY-MM-DD). Overrides lookback_days when used with end_date. - end_date: Optional end date (YYYY-MM-DD). Overrides lookback_days when used with start_date. ⚠️ DATE CLARIFICATION: If the user's date request is vague or ambiguous (e.g., "March to June" without a year, "last quarter", "recently", "a few months ago"), ask the user to specify exact dates before calling this tool. Do not assume or guess dates. - objective: 'conversions' (default), 'traffic', or 'awareness' - for optimal mix recommendations - target_roas: Optional override (default: from account goals or 2.0x) - ad_account_id: Required for multi-account users. Get from list_connected_accounts Execution time: 2-5 seconds (cached database query with analysis) Data source: meta_placement_daily_metrics table (placement-level daily metrics) ROAS Thresholds for Recommendations: - ✅ SCALE (ROAS ≥3.0x): Increase budget by 20-30% - ➖ MAINTAIN (ROAS 1.5-3.0x): Keep current budget - ⚠️ REDUCE (ROAS 1.0-1.5x): Reduce budget by 30-50% - 🔴 EXCLUDE (ROAS `<`1.0x): Remove from campaigns Meta Placements Analyzed: - Facebook: Feed, Stories, Reels, Marketplace, Search Results - Instagram: Feed, Stories, Reels, Explore - Messenger: Inbox, Stories - Audience Network: All placements Common Insights: - Audience Network often has lowest ROAS for conversion campaigns - consider excluding - Instagram Feed and Reels typically have highest conversion rates - Stories are great for awareness but may have lower conversion rates - Facebook Marketplace can be effective for e-commerce

Optimize Meta Budget

curl --request POST \
  --url https://api.adspirer.ai/api/v1/tools/optimize_meta_budget/execute \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "arguments": {
    "date_range": "string",
    "end_date": "string",
    "lookback_days": 30,
    "raw_data": false,
    "start_date": "string",
    "target_roas": 1,
    "total_budget": 1
  }
}
'

{
  "data": {
    "quota": {
      "limit": 150,
      "period_end": "2026-05-01",
      "tier": "plus",
      "used": 42
    },
    "text": "(tool-specific textual output for optimize_meta_budget)"
  },
  "success": true,
  "tool": "optimize_meta_budget"
}