Skip to main content
Glama

Create a Meta campaign

ads_create_meta_campaign

Build a Meta campaign, ad set and ad, all PAUSED: an objective (traffic, engagement, awareness, video_views, lead_generation, conversions, app_promotion), a daily or lifetime budget in whole currency units (on the ad set, or on the campaign with budgetLevel campaign), start and end dates, an optional bid strategy, targeting from ads_list_targeting, and a creative: a new image, video or carousel (2-10 cards) with headline, body, description, callToAction and linkUrl, published as the Page and optionally as an Instagram account from ads_list_instagram_accounts; or an existing Page post or Instagram post to boost. Pass campaignId or adSetId to add to an existing campaign or ad set. Media are staged uploads ({ uploadId }) or HTTPS URLs. Set validateOnly true first to have Meta check it without creating anything. Before creating, confirm the objective, budget, dates, audience and creative with the user; nothing spends until ads_set_status activates it, which needs the user's explicit go-ahead. Reuse the same idempotencyKey when retrying.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "adAccountId": "<adAccountId>",
      "objective": "<objective>",
      "campaignName": "<campaignName>",
      "creative": "<creative>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "ads_create_meta_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
bidNo
adNameNo
budgetNo
adSetIdNo
endDateNo
pixelIdNo
creativeYes
platformNometa_ads, tiktok_ads or linkedin_ads. Needed only when the profile has more than one ad network and no accountId is given.
accountIdNoThe Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection.
objectiveYes
profileIdNoA profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree.
startDateNo
targetingNo
campaignIdNo
leadFormIdNo
adAccountIdYes
appStoreUrlNo
budgetLevelNoad_set
campaignNameYes
validateOnlyNo
applicationIdNo
idempotencyKeyYesA unique value per intended campaign, such as a UUID. Sent as the Idempotency-Key header.
conversionEventNo
instagramAccountIdNo
specialAdCategoriesNo
specialAdCategoryCountriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare non-read-only, open-world and non-destructive; the description adds the material behavior the agent cannot infer: everything is created PAUSED, no spend occurs until ads_set_status activates it, and that activation requires explicit user consent. The validateOnly dry-run path and idempotency-retry contract are also disclosed.

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?

Single dense paragraph, front-loaded with what gets created and its paused state, then inputs, then safety workflow. Every clause carries information, though the run-on construction makes the parameters hard to scan compared with a short bulleted breakdown.

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?

For a 26-parameter, deeply nested creation tool with no output schema, the description covers the lifecycle, the dry-run path and the gating on activation. The gaps are the return shape (no mention of what IDs come back) and compliance-sensitive fields such as specialAdCategories, which are neither described nor annotated.

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?

With only 15% schema coverage across 26 parameters, the description carries the burden and mostly delivers: budget is clarified as whole currency units with ad-set-vs-campaign placement via budgetLevel, media as staged uploads ({ uploadId }) or HTTPS URLs, carousel as 2-10 cards, and the role of bid, targeting and creative is stated. It leaves several parameters unmapped in both schema and prose, notably specialAdCategories, conversionEvent, pixelId, leadFormId, applicationId/appStoreUrl and instagramAccountId.

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?

Opens with a specific verb and resource plus the exact object graph it builds: "Build a Meta campaign, ad set and ad, all PAUSED." It enumerates the supported objective set and creative variants, which distinguishes it cleanly from ads_create_linkedin_campaign, ads_create_tiktok_campaign and ads_create_campaign.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing and routing: run validateOnly true first, confirm objective/budget/dates/audience/creative with the user, pass campaignId or adSetId to extend an existing structure, and pull inputs from ads_list_targeting and ads_list_instagram_accounts. It also states that reuse of the same idempotencyKey is required on retry.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources