Skip to main content
Glama

create_adset

Create a new ad set with required fields: name, campaign ID, budget, optimization goal, billing event, and targeting. 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

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAd set name
campaign_idYesParent campaign ID
daily_budgetNoDaily budget in currency cents (e.g. '5000' = $50.00)
lifetime_budgetNoLifetime budget in currency cents
optimization_goalYesOptimization goal: IMPRESSIONS, REACH, LINK_CLICKS, LANDING_PAGE_VIEWS, OFFSITE_CONVERSIONS, APP_INSTALLS, LEAD_GENERATION, VALUE, THRUPLAY, ENGAGED_USERS
billing_eventYesBilling event: IMPRESSIONS, LINK_CLICKS, APP_INSTALLS, THRUPLAY
bid_strategyNoBid strategy: LOWEST_COST_WITHOUT_CAP, LOWEST_COST_WITH_BID_CAP, COST_CAP, LOWEST_COST_WITH_MIN_ROAS
targetingYesJSON string of targeting spec (age_min, age_max, genders, geo_locations, interests, etc.)
start_timeNoStart time (ISO 8601)
end_timeNoEnd time (ISO 8601)
statusNoAd set status (default PAUSED)PAUSED
Behavior3/5

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

Annotations are absent, so description bears full burden. It notes default status 'PAUSED' which adds behavioral context, but does not disclose other traits like destructive nature, auth requirements, or side effects.

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 concise sentences front-loading the action and key requirements, with no wasted words.

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

Completeness2/5

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

With 11 parameters, no output schema, and no annotations, the description is brief but leaves gaps: no return value info, no error conditions, and no guidance on optional parameters.

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 baseline 3. The description only reiterates required parameters and defaults, adding no new semantic meaning 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?

Description clearly states 'Create a new ad set' and lists required fields (name, campaign_id, etc.), distinguishing it from sibling tools like copy_adset or update_adset.

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?

No explicit guidance on when to use create_adset over alternatives like copy_adset or create_campaign. The description lists required fields but does not provide context for tool selection.

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/mikusnuz/meta-ads-mcp'

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