Skip to main content
Glama

meta_ads_ad_sets_create

Create ad sets within existing Meta Ads campaigns. Specify targeting (geo locations, age ranges), daily budget, billing event, and optimization goal. Default status is PAUSED for operator review before activation.

Instructions

Creates a new ad set inside an existing campaign. Returns the new ad_set id. Mutating, reversible via rollback_apply (rollback sets status to PAUSED). Targeting is passed as a Meta targeting spec object; at minimum supply geo_locations and age bounds. Default initial status is PAUSED — only ACTIVE when the operator has confirmed spend. After creation, attach ads with meta_ads_ads_create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
campaign_idYesParent campaign ID. Must exist and not be DELETED.
nameYesAd set name, up to 400 characters.
daily_budgetNoDaily budget in account currency minor units (cents for USD, yen for JPY). Required unless the parent campaign uses CBO; mutually exclusive with lifetime-budget settings on the same ad set.
billing_eventNoWhat Meta charges for. Default IMPRESSIONS. The valid options depend on the optimization_goal — incompatible pairings are rejected by Meta.
optimization_goalNoWhat Meta optimises delivery for (e.g. REACH, LINK_CLICKS, OFFSITE_CONVERSIONS, LANDING_PAGE_VIEWS, THRUPLAY). Default REACH. Must be compatible with the parent campaign's objective.
targetingNoMeta targeting spec. Typical keys: geo_locations (e.g. {'countries': ['JP']}), age_min, age_max, genders, interests, custom_audiences. See Meta Marketing API targeting docs for the full schema.
statusNoInitial status. Default PAUSED. Only ACTIVE after operator sign-off.
bid_amountNoBid cap in account currency minor units. Required for bid-strategy optimization goals such as LINK_CLICKS with TARGET_COST. Omit for automatic bidding.
Behavior4/5

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

With no annotations, the description discloses key behaviors: it is mutating, reversible via rollback_apply, default status PAUSED, and only ACTIVE after operator confirmation. This adds value beyond the schema.

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?

Four sentences, front-loaded with main purpose, no redundancy. Every sentence adds value.

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 creation tool with 9 parameters and no output schema, the description covers return value, lifecycle (rollback, default status), and workflow (attach ads). Complete for correct invocation.

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 100%, and the description adds practical context for each parameter: account_id fallback, campaign_id existence, daily_budget CBO rule, billing_event compatibility, targeting typical keys, status default, bid_amount requirement. This goes beyond the schema.

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 states 'Creates a new ad set inside an existing campaign. Returns the new ad_set id.' It uses a specific verb (creates) and resource (ad set), and distinguishes from sibling tools like meta_ads_ads_create (attaches ads) and meta_ads_campaigns_create (creates campaigns).

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?

The description provides context on when to use: it mentions targeting requirements, default status, and the next step (attach ads). It does not explicitly state when not to use or alternatives, but the workflow is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server