Adbloop Meta Ads

create_structured

Destructive

Create ONE campaign with MULTIPLE ad sets and MULTIPLE ads each (1 campaign -> N ad sets -> M ads), image or video, including DPA/Catalog dynamic product ads. Created PAUSED. Honors spend guardrails. Pro feature. WRITES live.

Input Schema

Name	Required	Description	Default
`campaigns`	Yes	One or more structured campaigns (usually one).
`meta_account_id`	No	Ad account (defaults to primary).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

addedInput schema / properties / campaigns / items / properties / adSets / items / properties / customAudiences

Added value: +{
+  "description": "Optional — custom/lookalike audience ids to target (from list_custom_audiences, Pro).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / campaigns / items / properties / adSets / items / properties / excludedAudiences

Added value: +{
+  "description": "Optional — audience ids to exclude, e.g. past buyers.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed4 schema fields changedOct 10, 2026

addedInput schema / properties / campaigns / items / properties / adSets / items / properties / budgetType

Added value: +{
+  "description": "ABO only. LIFETIME needs lifetimeBudget and scheduleEnd.",
+  "enum": [
+    "DAILY",
+    "LIFETIME"
+  ],
+  "type": "string"
+}

addedInput schema / properties / campaigns / items / properties / adSets / items / properties / lifetimeBudget

Added value: +{
+  "description": "Lifetime budget MAJOR units (ABO, budgetType LIFETIME).",
+  "type": "number"
+}

addedInput schema / properties / campaigns / items / properties / adSets / items / properties / scheduleEnd

Added value: +{
+  "description": "Ad set end, ISO 8601. Required (more than 24h after start) with a lifetime budget.",
+  "type": "string"
+}

addedInput schema / properties / campaigns / items / properties / adSets / items / properties / scheduleStart
```
Added value: +{
+  "description": "Ad set start, ISO 8601.",
+  "type": "string"
+}
```

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / campaigns / items / properties / adSets / items / properties / geoLocations

Added value: +{
+  "additionalProperties": true,
+  "description": "OPTIONAL specific places instead of whole countries (replaces countries when set). Get keys from search_locations. cities: [{ key, radius (km, 17-80; omit for the city only), country_code }], regions: [{ key, country_code }] (states), zips: [{ key e.g. \"IN:380015\", country_code }] (PIN/ZIP codes). Meta rejects overlapping places (e.g. a PIN inside a city radius). With a Special Ad Category: no zips, and cities need a radius of at least 25 km.",
+  "properties": {
+    "cities": {
+      "items": {
+        "properties": {
+          "country_code": {
+            "type": "string"
+          },
+          "key": {
+            "type": "string"
+          },
+          "radius": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "key"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "regions": {
+      "items": {
+        "properties": {
+          "country_code": {
+            "type": "string"
+          },
+          "key": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "key"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "zips": {
+      "items": {
+        "properties": {
+          "country_code": {
+            "type": "string"
+          },
+          "key": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "key"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / campaigns / items / properties / geoLocations

Added value: +{
+  "additionalProperties": true,
+  "description": "OPTIONAL specific places instead of whole countries (replaces countries when set). Get keys from search_locations. cities: [{ key, radius (km, 17-80; omit for the city only), country_code }], regions: [{ key, country_code }] (states), zips: [{ key e.g. \"IN:380015\", country_code }] (PIN/ZIP codes). Meta rejects overlapping places (e.g. a PIN inside a city radius). With a Special Ad Category: no zips, and cities need a radius of at least 25 km.",
+  "properties": {
+    "cities": {
+      "items": {
+        "properties": {
+          "country_code": {
+            "type": "string"
+          },
+          "key": {
+            "type": "string"
+          },
+          "radius": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "key"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "regions": {
+      "items": {
+        "properties": {
+          "country_code": {
+            "type": "string"
+          },
+          "key": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "key"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "zips": {
+      "items": {
+        "properties": {
+          "country_code": {
+            "type": "string"
+          },
+          "key": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "key"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedJun 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses important behavior: the campaign is created PAUSED, it writes live, it honors spend guardrails, and it is a Pro feature. These are exactly the safety and operational details an agent needs before invoking a mutating creation tool.

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?

The description is compact and front-loaded, stating the core creation shape first and then safety and feature notes. Every phrase carries useful information without redundancy.

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 complex destructive creation tool with rich schema coverage and annotations, the description covers the essential scope, safety posture, and special DPA/Catalog capability. It is nearly complete, though it could be stronger with explicit sibling routing or return-behavior guidance.

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 the nested campaign, ad set, ad, geo, and DPA fields are already documented in the input schema. The description adds the high-level cardinality model, but it does not add parameter-level meaning beyond what the schema provides.

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 uses a specific verb and resource: creating a structured campaign hierarchy with one campaign, multiple ad sets, and multiple ads each. It also distinguishes the tool's scope by calling out image/video and DPA/Catalog support, which helps separate it from simpler sibling creation tools.

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?

The description gives clear context for when this tool applies: one campaign with many ad sets and many ads, including DPA/Catalog dynamic product ads. It does not explicitly name alternatives such as create_campaign or bulk_create_campaigns, so routing still requires inference.

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

All Adbloop Meta Ads tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?