Skip to main content
Glama

create_adset

Create a paused ad set with automatic pre-write validation: checks parent campaign, enforces Advantage+ or manual audience, handles ABO/CBO budgets, maps ICP signals, and verifies post-write for compliance.

Instructions

Create a new ad set (always PAUSED, no exceptions).

Runs Advantage+ audience enforcement, parent campaign inspection, ABO/CBO enforcement, ICP signal mapping, narrowing detection, pre-write validation, creates the ad set, and verifies post-write.

Args: account_id: Ad account ID (e.g., 'act_123456789'). campaign_id: Parent campaign ID. Must be PAUSED or ACTIVE. name: Ad set name. Greek text validated. optimization_goal: e.g. 'OFFSITE_CONVERSIONS', 'LINK_CLICKS', 'LEAD_GENERATION', 'REACH'. Must be compatible with parent campaign objective. billing_event: Usually 'IMPRESSIONS'. Also: 'LINK_CLICKS', 'THRUPLAY'. daily_budget: Daily budget in EUR (e.g., 15.00). Required for ABO campaigns. Omit for CBO. lifetime_budget: Lifetime budget in EUR. Alternative to daily_budget. Requires end_time. targeting_json: JSON string of targeting spec. Advantage+ mode uses signals as suggestions. Example: '{"geo_locations":{"countries":["GR"]},"age_min":25,"age_max":55}' promoted_object_json: JSON string of promoted object. Required for OUTCOME_SALES/LEADS. Example: '{"pixel_id":"123456789012345","custom_event_type":"PURCHASE"}' start_time: ISO 8601 start time. Optional (defaults to immediately when activated). end_time: ISO 8601 end time. Required if using lifetime_budget. audience_mode: 'advantage_plus' (default, recommended), 'manual', 'broad', 'existing_audience', 'restricted' (disables Advantage+). icp_name: ICP name from concept selection for signal derivation. icp_signals_json: Pre-built ICP signals JSON with interests/behaviors/demographics. experiment_type: If 'strict_audience_test', allows Advantage+ OFF. explicit_tracking_mode: Operator-declared tracking mode override. 'instant_form', 'messaging', 'page_engagement' allow writes without pixel. If not set, system infers intended flow and enforces pixel for website paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
campaign_idYes
nameYes
optimization_goalYes
billing_eventNoIMPRESSIONS
daily_budgetNo
lifetime_budgetNo
targeting_jsonNo
promoted_object_jsonNo
start_timeNo
end_timeNo
audience_modeNoadvantage_plus
icp_nameNo
icp_signals_jsonNo
experiment_typeNo
explicit_tracking_modeNo
naming_audience_typeNo
naming_age_rangeNo
naming_geoNoGR
naming_exclusion_flagNoNone
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses that ad sets are always PAUSED, enumerates validations and enforcement steps (Advantage+ audience, ABO/CBO, ICP mapping, etc.). No contradictions.

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

Conciseness4/5

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

Front-loaded with the critical 'always PAUSED' fact. Structured with Args and bullet points. Slightly verbose due to parameter explanations, but justified by tool complexity (20 parameters).

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?

Covers input parameters thoroughly and explains validations. Does not describe return value or error handling, but for a creation tool with standard output, this gap is minor given the schema absence.

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

Parameters5/5

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

Schema coverage is 0% but the description's Args section explains each parameter in detail, adding value beyond the schema's minimal titles. Provides examples and usage notes for complex fields like targeting_json.

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 clearly states it creates a new ad set that is always PAUSED. It lists the extensive steps involved, distinguishing it from siblings like update_adset or duplicate_adset.

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?

Provides prerequisites (campaign_id must be PAUSED or ACTIVE) and explains budget rules (daily_budget for ABO, omit for CBO). Does not explicitly contrast with alternative tools, but usage context 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/brandu-mos/konquest-meta-ads-mcp'

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