Skip to main content
Glama

create_adset

Create a new Meta ad set for a campaign by specifying budget, optimization goal, billing event, and targeting; it defaults to PAUSED status.

Instructions

Create a new ad set. Requires name, campaign_id, budget, optimization_goal, billing_event, and targeting. Defaults to PAUSED status.

Input Schema

NameRequiredDescriptionDefault
nameYesAd set name
statusNoAd set status (default PAUSED)PAUSED
end_timeNoEnd time (ISO 8601)
dsa_payorNoPayer of EU-targeted ads; does not automatically copy dsa_beneficiary. May use the account's saved default.
targetingYesJSON string of targeting spec (age_min, age_max, genders, geo_locations, interests, etc.). Advantage+ Audience automation and other flags go inside this object too, e.g. targeting_automation: {"advantage_audience":1}. As of v26.0, ad sets in the Housing, Employment, or Financial Products and Services (HEC-F) special ad categories with relaxable (non-broad) targeting must explicitly set targeting.targeting_automation.advantage_audience to 1 or 0 — omitting it now returns ADS_TARGETING__REQUIRE_EXPLICIT_ADVANTAGE_AUDIENCE_FLAG. Not required for broad/default audience setups. Also note: as of Marketing API v26.0, the Instagram Explore Feed placement was removed (explicitly specifying it in publisher_platforms/instagram_positions now returns an error) and the 'story' value in messenger_positions is silently dropped.
account_idNoAd account ID to create the ad set in (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.
bid_amountNoBid amount in the account currency's minor unit. Required for COST_CAP or LOWEST_COST_WITH_BID_CAP except Reach and Frequency.
start_timeNoStart time (ISO 8601)
campaign_idYesParent campaign ID
pacing_typeNoPacing settings. When a schedule is supplied, day_parting is required and is added if omitted.
bid_strategyNoBid strategy: LOWEST_COST_WITHOUT_CAP, LOWEST_COST_WITH_BID_CAP, COST_CAP, LOWEST_COST_WITH_MIN_ROAS
daily_budgetNoDaily budget in currency cents (e.g. '5000' = $50.00)
billing_eventYesBilling event: APP_INSTALLS, CLICKS, IMPRESSIONS, LINK_CLICKS, NONE, OFFER_CLAIMS, PAGE_LIKES, POST_ENGAGEMENT, THRUPLAY, PURCHASE, LISTING_INTERACTION
validate_onlyNoValidate with Meta without creating or updating the ad set (default false)
adset_scheduleNoHourly delivery intervals (Sunday=0). Requires lifetime budgeting. Set timezone_type explicitly; Meta defaults to USER.
dsa_beneficiaryNoBeneficiary of EU-targeted ads; may use the account's saved default when omitted
lifetime_budgetNoLifetime budget in currency cents
promoted_objectNoJSON string of the promoted_object spec. Required for many objectives, e.g. OUTCOME_SALES needs {"pixel_id":"...","custom_event_type":"PURCHASE"}, OUTCOME_APP_PROMOTION needs {"application_id":"...","object_store_url":"..."}, OUTCOME_ENGAGEMENT page-like ads need {"page_id":"..."}. Omitting it when the objective requires one causes ad set creation to fail.
attribution_specNoAttribution windows; Meta validates compatibility with the objective and optimization goal
destination_typeNoConversion destination, e.g. WEBSITE, APP, MESSENGER, INSTAGRAM_DIRECT, WHATSAPP
optimization_goalYesOptimization goal: NONE, APP_INSTALLS, AD_RECALL_LIFT, ENGAGED_USERS, EVENT_RESPONSES, IMPRESSIONS, LEAD_GENERATION, QUALITY_LEAD, LINK_CLICKS, OFFSITE_CONVERSIONS, PAGE_LIKES, POST_ENGAGEMENT, QUALITY_CALL, REACH, LANDING_PAGE_VIEWS, VISIT_INSTAGRAM_PROFILE, ENGAGED_PAGE_VIEWS, VALUE, THRUPLAY, DERIVED_EVENTS, APP_INSTALLS_AND_OFFSITE_CONVERSIONS, CONVERSATIONS, IN_APP_VALUE, MESSAGING_PURCHASE_CONVERSION, MESSAGING_DEEP_CONVERSATION_AND_FOLLOW, SUBSCRIBERS, REMINDERS_SET, MEANINGFUL_CALL_ATTEMPT, PROFILE_VISIT, PROFILE_AND_PAGE_ENGAGEMENT, ADVERTISER_SILOED_VALUE, AUTOMATIC_OBJECTIVE, MESSAGING_APPOINTMENT_CONVERSION

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.6.1
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Ad account ID to create the ad set in (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.",
      +  "type": "string"
      +}
    • addedInput schema / properties / adset_schedule
      Added value: +{
      +  "description": "Hourly delivery intervals (Sunday=0). Requires lifetime budgeting. Set timezone_type explicitly; Meta defaults to USER.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "days": {
      +        "items": {
      +          "maximum": 6,
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "maxItems": 7,
      +        "minItems": 1,
      +        "type": "array"
      +      },
      +      "end_minute": {
      +        "maximum": 1440,
      +        "minimum": 1,
      +        "type": "integer"
      +      },
      +      "start_minute": {
      +        "maximum": 1439,
      +        "minimum": 0,
      +        "type": "integer"
      +      },
      +      "timezone_type": {
      +        "enum": [
      +          "USER",
      +          "ADVERTISER"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "start_minute",
      +      "end_minute",
      +      "days"
      +    ],
      +    "type": "object"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedInput schema / properties / attribution_spec
      Added value: +{
      +  "description": "Attribution windows; Meta validates compatibility with the objective and optimization goal",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "event_type": {
      +        "enum": [
      +          "CLICK_THROUGH",
      +          "VIEW_THROUGH",
      +          "ENGAGED_VIDEO_VIEW"
      +        ],
      +        "type": "string"
      +      },
      +      "weight": {
      +        "type": "number"
      +      },
      +      "window_days": {
      +        "exclusiveMinimum": 0,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "event_type",
      +      "window_days"
      +    ],
      +    "type": "object"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedInput schema / properties / bid_amount
      Added value: +{
      +  "description": "Bid amount in the account currency's minor unit. Required for COST_CAP or LOWEST_COST_WITH_BID_CAP except Reach and Frequency.",
      +  "pattern": "^\\d+$",
      +  "type": "string"
      +}
    • changedInput schema / properties / billing_event / description
      Previous value: -"Billing event: IMPRESSIONS, LINK_CLICKS, APP_INSTALLS, THRUPLAY"New value: +"Billing event: APP_INSTALLS, CLICKS, IMPRESSIONS, LINK_CLICKS, NONE, OFFER_CLAIMS, PAGE_LIKES, POST_ENGAGEMENT, THRUPLAY, PURCHASE, LISTING_INTERACTION"
    • addedInput schema / properties / destination_type
      Added value: +{
      +  "description": "Conversion destination, e.g. WEBSITE, APP, MESSENGER, INSTAGRAM_DIRECT, WHATSAPP",
      +  "type": "string"
      +}
    • addedInput schema / properties / dsa_beneficiary
      Added value: +{
      +  "description": "Beneficiary of EU-targeted ads; may use the account's saved default when omitted",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / dsa_payor
      Added value: +{
      +  "description": "Payer of EU-targeted ads; does not automatically copy dsa_beneficiary. May use the account's saved default.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / optimization_goal / description
      Previous value: -"Optimization goal: IMPRESSIONS, REACH, LINK_CLICKS, LANDING_PAGE_VIEWS, OFFSITE_CONVERSIONS, APP_INSTALLS, LEAD_GENERATION, VALUE, THRUPLAY, ENGAGED_USERS"New value: +"Optimization goal: NONE, APP_INSTALLS, AD_RECALL_LIFT, ENGAGED_USERS, EVENT_RESPONSES, IMPRESSIONS, LEAD_GENERATION, QUALITY_LEAD, LINK_CLICKS, OFFSITE_CONVERSIONS, PAGE_LIKES, POST_ENGAGEMENT, QUALITY_CALL, REACH, LANDING_PAGE_VIEWS, VISIT_INSTAGRAM_PROFILE, ENGAGED_PAGE_VIEWS, VALUE, THRUPLAY, DERIVED_EVENTS, APP_INSTALLS_AND_OFFSITE_CONVERSIONS, CONVERSATIONS, IN_APP_VALUE, MESSAGING_PURCHASE_CONVERSION, MESSAGING_DEEP_CONVERSATION_AND_FOLLOW, SUBSCRIBERS, REMINDERS_SET, MEANINGFUL_CALL_ATTEMPT, PROFILE_VISIT, PROFILE_AND_PAGE_ENGAGEMENT, ADVERTISER_SILOED_VALUE, AUTOMATIC_OBJECTIVE, MESSAGING_APPOINTMENT_CONVERSION"
    • addedInput schema / properties / pacing_type
      Added value: +{
      +  "description": "Pacing settings. When a schedule is supplied, day_parting is required and is added if omitted.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / promoted_object
      Added value: +{
      +  "description": "JSON string of the promoted_object spec. Required for many objectives, e.g. OUTCOME_SALES needs {\"pixel_id\":\"...\",\"custom_event_type\":\"PURCHASE\"}, OUTCOME_APP_PROMOTION needs {\"application_id\":\"...\",\"object_store_url\":\"...\"}, OUTCOME_ENGAGEMENT page-like ads need {\"page_id\":\"...\"}. Omitting it when the objective requires one causes ad set creation to fail.",
      +  "type": "string"
      +}
    • changedInput schema / properties / targeting / description
      Previous value: -"JSON string of targeting spec (age_min, age_max, genders, geo_locations, interests, etc.)"New value: +"JSON string of targeting spec (age_min, age_max, genders, geo_locations, interests, etc.). Advantage+ Audience automation and other flags go inside this object too, e.g. targeting_automation: {\"advantage_audience\":1}. As of v26.0, ad sets in the Housing, Employment, or Financial Products and Services (HEC-F) special ad categories with relaxable (non-broad) targeting must explicitly set targeting.targeting_automation.advantage_audience to 1 or 0 — omitting it now returns ADS_TARGETING__REQUIRE_EXPLICIT_ADVANTAGE_AUDIENCE_FLAG. Not required for broad/default audience setups. Also note: as of Marketing API v26.0, the Instagram Explore Feed placement was removed (explicitly specifying it in publisher_platforms/instagram_positions now returns an error) and the 'story' value in messenger_positions is silently dropped."
    • addedInput schema / properties / validate_only
      Added value: +{
      +  "description": "Validate with Meta without creating or updating the ad set (default false)",
      +  "type": "boolean"
      +}
  2. First observedv1.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the creation default ('Defaults to PAUSED status'), which tells the agent the new ad set will not immediately spend, but omits permissions/auth requirements, whether creation is idempotent, and what happens on failure.

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?

Two short sentences, no padding, with the core action front-loaded and the operational default (PAUSED) trailing. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 21-parameter create tool with no annotations and no output schema, the description is thin: it never states what is returned (e.g. the new ad set ID) nor flags interplay among the budget/bid_strategy parameters. The rich schema compensates for parameter detail, but the description leaves the agent to infer creation behavior and outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 21 parameters in depth, setting the baseline at 3. The description only restates a subset of required fields and adds no syntax or format meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a new ad set'), which clearly separates it from create_campaign, create_ad, and update_adset by noun. It does not explicitly name or contrast with any sibling, but the resource is unambiguous enough that an agent can select it correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description lists required fields but gives no when-to-use guidance, no prerequisites, and no alternatives (e.g. update_adset vs create_adset). It also references a 'budget' requirement that does not map to any single parameter (there are daily_budget, lifetime_budget, and bid_amount), so the guidance it does offer is imprecise.

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

Deploy Server

Other Tools