Skip to main content
Glama
Green-pep

meta-ads-mcp-patched

by Green-pep

create_adset

Create a Meta Ads ad set by supplying campaign ID, budget, targeting, optimization goal, and billing event. New ad sets default 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
statusNoAd set status (default PAUSED)PAUSED
end_timeNoEnd time (ISO 8601)
dsa_payorNoWho pays for the ad (legal entity name). Required with dsa_beneficiary for EU-delivering ad sets (DSA)
targetingYesJSON string of targeting spec (age_min, age_max, genders, geo_locations, interests, etc.)
bid_amountNoBid cap / target cost in currency cents. Required by Meta when the effective bid strategy is LOWEST_COST_WITH_BID_CAP or COST_CAP
start_timeNoStart time (ISO 8601)
campaign_idYesParent campaign ID
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: IMPRESSIONS, LINK_CLICKS, APP_INSTALLS, THRUPLAY
dsa_beneficiaryNoWho benefits from the ad (legal entity name, shown in the EU Ad Library). Required by Meta for any ad set delivering into the EU (DSA)
lifetime_budgetNoLifetime budget in currency cents
promoted_objectNoJSON string of the promoted object. Required for LEAD_GENERATION ({"page_id":"..."}) and OFFSITE_CONVERSIONS ({"pixel_id":"...","custom_event_type":"..."})
optimization_goalYesOptimization goal: IMPRESSIONS, REACH, LINK_CLICKS, LANDING_PAGE_VIEWS, OFFSITE_CONVERSIONS, APP_INSTALLS, LEAD_GENERATION, VALUE, THRUPLAY, ENGAGED_USERS
Behavior2/5

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

With no annotations, the description must carry full behavioral disclosure, but it only reveals the default PAUSED status. It omits details about return values, required permissions, error conditions, or the side effects of creation.

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?

One concise sentence, front-loaded with the action. However, the incorrect 'budget' requirement taints the content, preventing a perfect score.

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?

For a tool with 15 parameters and no output schema, the description is too terse. It doesn't mention what the API returns (e.g., ad set ID), potential validation errors, or any additional context needed for successful invocation.

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

Parameters2/5

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

Schema coverage is 100%, so baseline is 3, but the description does not add value beyond the schema. Worse, it incorrectly states that budget is required when it is not in the schema, actively misleading the agent and lowering the score.

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?

Clearly states the action and resource: 'Create a new ad set.' This distinguishes it from update/delete/copy siblings. However, it lists 'budget' as required, which the schema does not require, creating a slight ambiguity about the tool's exact contract.

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 guidance on when to use this tool versus alternatives. It does not mention that update_adset should be used for modifying existing ad sets, nor does it provide context on prerequisites or when not to use it.

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/Green-pep/meta-ads-mcp-patched'

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