Skip to main content
Glama

Adbloop Meta Ads

by com.adbloop
OverviewDiscussionsAdmin

bulk_create_campaigns

Create many Meta campaigns at once on ONE account (rate-limit-safe, validated). WRITES live. Honors plan limits, spend guardrails, and capacity. Auto-uses the correct Page/Instagram/pixel. Each campaign needs an imageUrl (public image, or Drive/Dropbox share link).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoSet true to proceed when a spend-guardrail or rate-limit-capacity warning would otherwise pause the run.
page_idNoFacebook Page for the ads. Optional — auto-resolved from the account if omitted.
pixel_idNoMeta Pixel for conversion tracking. Optional — auto-resolved from the account if omitted.
campaignsYesThe campaigns to create; each item's fields are defined in the campaign schema. campaignName and objective are required per campaign; image ads need an imageUrl.
catalogIdNoProduct catalog ID, for DPA / catalog (dynamic product) campaigns.
productSetIdNoProduct set ID within the catalog, for DPA / catalog campaigns.
meta_account_idNoAd account to create all these campaigns on (defaults to your primary account).
instagram_account_idNoInstagram account for placements. Optional — auto-resolved from the account if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed8 schema fields changed
    • addedInput schema / properties / campaigns / description
      Added value: +"The campaigns to create; each item's fields are defined in the campaign schema. campaignName and objective are required per campaign; image ads need an imageUrl."
    • addedInput schema / properties / catalogId / description
      Added value: +"Product catalog ID, for DPA / catalog (dynamic product) campaigns."
    • addedInput schema / properties / confirm / description
      Added value: +"Set true to proceed when a spend-guardrail or rate-limit-capacity warning would otherwise pause the run."
    • addedInput schema / properties / instagram_account_id / description
      Added value: +"Instagram account for placements. Optional — auto-resolved from the account if omitted."
    • addedInput schema / properties / meta_account_id / description
      Added value: +"Ad account to create all these campaigns on (defaults to your primary account)."
    • addedInput schema / properties / page_id / description
      Added value: +"Facebook Page for the ads. Optional — auto-resolved from the account if omitted."
    • addedInput schema / properties / pixel_id / description
      Added value: +"Meta Pixel for conversion tracking. Optional — auto-resolved from the account if omitted."
    • addedInput schema / properties / productSetId / description
      Added value: +"Product set ID within the catalog, for DPA / catalog campaigns."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false; the description goes well beyond that by stating it WRITES live, is rate-limit-safe and validated, honors plan limits, spend guardrails and capacity, and auto-resolves Page/Instagram/pixel. That is genuinely useful behavioral context, though it omits partial-failure behavior and how success is reported.

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?

Five compact sentences, front-loaded with the core action and scope, then the safety/auto-resolution qualifiers. Every sentence carries weight, though the imageUrl sentence slightly overstates the requirement (schema makes it conditional on image ads).

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 bulk-write tool with no output schema and only a readOnlyHint annotation, the description covers write semantics, guardrails, capacity and auto-resolution. It stops short of mentioning prerequisite siblings like validate_campaigns or estimate_bulk_create, but nothing essential to calling it correctly is missing.

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 baseline is 3; the description's only added param meaning is the imageUrl note (public image or Drive/Dropbox share link), which the schema already documents in detail. No syntax or format detail beyond the schema is contributed.

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?

States a specific verb and resource ('Create many Meta campaigns at once') and scopes it to 'ONE account', which cleanly separates it from bulk_create_multi_account and the singular create_campaign. An agent can route to it without opening the schema.

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

Usage Guidelines3/5

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

The 'on ONE account' scoping and 'rate-limit-safe, validated' framing imply when this is appropriate, but no sibling is named as the alternative (e.g. bulk_create_multi_account for multi-account) and there is no explicit when-not guidance. Usage is inferable but not spelled out.

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 toolsInspect
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