Skip to main content
Glama
swesmith-repos

Meta Ads MCP

create_adset

Create a new ad set within a Meta Ads campaign to define targeting, budget, and optimization settings for your Facebook and Instagram ads.

Instructions

Create a new ad set in a Meta Ads account.

Args:
    account_id: Meta Ads account ID (format: act_XXXXXXXXX)
    campaign_id: Meta Ads campaign ID this ad set belongs to
    name: Ad set name
    optimization_goal: Conversion optimization goal (e.g., 'LINK_CLICKS', 'REACH', 'CONVERSIONS', 'APP_INSTALLS')
    billing_event: How you're charged (e.g., 'IMPRESSIONS', 'LINK_CLICKS')
    status: Initial ad set status (default: PAUSED)
    daily_budget: Daily budget in account currency (in cents) as a string
    lifetime_budget: Lifetime budget in account currency (in cents) as a string
    targeting: Targeting specifications including age, location, interests, etc.
              Use targeting_automation.advantage_audience=1 for automatic audience finding
    bid_amount: Bid amount in account currency (in cents)
    bid_strategy: Bid strategy (e.g., 'LOWEST_COST', 'LOWEST_COST_WITH_BID_CAP')
    start_time: Start time in ISO 8601 format (e.g., '2023-12-01T12:00:00-0800')
    end_time: End time in ISO 8601 format
    dsa_beneficiary: DSA beneficiary (person/organization benefiting from ads) for European compliance
    promoted_object: Mobile app configuration for APP_INSTALLS campaigns. Required fields: application_id, object_store_url.
                    Optional fields: custom_event_type, pixel_id, page_id.
                    Example: {"application_id": "123456789012345", "object_store_url": "https://apps.apple.com/app/id123456789"}
    destination_type: Where users are directed after clicking the ad (e.g., 'APP_STORE', 'DEEPLINK', 'APP_INSTALL', 'ON_AD').
                      Required for mobile app campaigns and lead generation campaigns.
                      Use 'ON_AD' for lead generation campaigns where user interaction happens within the ad.
    is_dynamic_creative: Enable Dynamic Creative for this ad set (required when using dynamic creatives with asset_feed_spec/dynamic_creative_spec).
    access_token: Meta API access token (optional - will use cached token if not provided)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
campaign_idYes
nameYes
optimization_goalYes
billing_eventYes
statusNoPAUSED
daily_budgetNo
lifetime_budgetNo
targetingNo
bid_amountNo
bid_strategyNo
start_timeNo
end_timeNo
dsa_beneficiaryNo
promoted_objectNo
destination_typeNo
is_dynamic_creativeNo
access_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation tool (implying mutation), but doesn't mention permissions needed, whether creation is reversible, rate limits, or what happens on success/failure. The description adds some context about default status and optional parameters but lacks critical behavioral information for a mutation tool.

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

Conciseness3/5

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

The description is appropriately front-loaded with the core purpose, but the parameter documentation section is lengthy (18 items). While each parameter explanation earns its place given the 0% schema coverage, the overall structure could be more streamlined with grouping or categorization of related 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?

Given the tool's complexity (18 parameters, mutation operation, no annotations) and the existence of an output schema, the description provides substantial context. It thoroughly documents parameters and includes practical examples and usage notes. The main gap is lack of behavioral context around permissions, side effects, and error handling that would be expected for a creation tool.

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?

With 0% schema description coverage for 18 parameters, the description provides extensive parameter semantics that fully compensate. It explains each parameter's purpose, format requirements, examples, and special conditions (e.g., 'required for mobile app campaigns', 'use targeting_automation.advantage_audience=1', 'default: PAUSED'). This adds significant value beyond the bare 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 clearly states the tool creates a new ad set in a Meta Ads account, specifying both the verb ('create') and resource ('ad set'). It distinguishes from siblings like create_ad, create_campaign, and update_adset by focusing specifically on ad set creation rather than other ad objects or updates.

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 provides no guidance on when to use this tool versus alternatives like update_adset or create_campaign. While it mentions the tool creates ad sets within campaigns, it doesn't specify prerequisites, dependencies, or scenarios where this tool is appropriate versus other creation tools in the sibling list.

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/swesmith-repos/pipeboard-co__meta-ads-mcp.36128861'

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