Meta Ads Operator for Openclaw

Meta Ads Operator turns briefs into controlled Meta Ads campaign builds with documented rationale, naming, UTM, and paused-by-default execution.

moskoweb
v1.0.0
Jul 31, 2026
0
436
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install meta-ads-operator

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install meta-ads-operator using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Meta Ads Operator?

Meta Ads Operator is an Openclaw Skills package for planning, building, and editing Meta Ads campaigns through any connected Meta Ads MCP. It translates a business brief into a clean operational structure, then executes the build with guardrails that prioritize clarity, tracking consistency, and safe launch practices.

This skill is designed for operators who need repeatable campaign architecture rather than ad hoc setup. It enforces a paused-first workflow, requires rationale before publish, and keeps naming, UTMs, and tracking treated as part of the campaign infrastructure. The result is a more auditable and scalable Meta Ads process across campaign creation, ad set design, creative assembly, and controlled edits.

Meta Ads Operator Use Cases

  • When you need to create a new Meta Ads campaign, ad set, ad, or creative.
  • When a user asks for campaign structure planning from a brief.
  • When you need to edit existing Meta Ads assets in a controlled way.
  • When a launch checklist, readiness check, or maintenance workflow is required.
  • When you want a standardized Openclaw Skills process for Meta Ads operations across different MCP providers.

How Meta Ads Operator Works

  1. Detect the connected Meta Ads MCP and discover available tools.
  2. Read the campaign brief and convert it into a business objective and operational plan.
  3. Choose the campaign architecture, including campaign, ad set, ad, and creative structure.
  4. Define naming conventions and UTM parameters as part of the tracking foundation.
  5. Validate account readiness, setup, creative status, and tracking integrity.
  6. Build all new assets in PAUSED state by default.
  7. Record the rationale and finalize the launch or edit checklist.
  8. If a requested capability is unavailable in the connected MCP, mark it as out of scope and signal the limitation clearly.

Meta Ads Operator Setup

  1. Ensure a Meta Ads MCP is connected to the agent.
  2. Confirm the MCP exposes the needed capabilities for campaign, ad set, creative, and ad management.
  3. Perform tool discovery so the skill can map skill requirements to the MCP's actual tool names.
  4. Verify that account access, permissions, and tracking setup are available before building.
  5. Review the reference playbooks in the skill directory for naming, structure, creative, and launch standards.
# Example: inspect the skill references and confirm the connected MCP environment
ls {baseDir}/references/
# Example: validate the required operational docs are present
cat {baseDir}/references/launch-checklist.md
cat {baseDir}/references/official-meta-build-guidelines.md
  1. Map the connected MCP tools to the required actions:
  • list accounts and campaigns
  • create/update/pause/resume campaigns
  • list/create ad sets
  • list/create/validate creatives
  • list/create/update/pause ads
  • diagnose readiness and creative issues
  1. If any required capability is missing, treat it as out of scope and report it before attempting execution.

Meta Ads Operator Data Schema & Taxonomy

The skill organizes its operational data around campaign-build artifacts, references, and execution metadata. Its structure is intentionally lightweight so it can work with any connected Meta Ads MCP while still producing consistent output.

Area Purpose Notes
references/ Authoritative playbooks and standards Contains build, structure, creative, launch, editing, and official Meta guidelines
Campaign architecture Business-to-platform translation layer Defines campaign, ad set, ad, and creative structure
Naming conventions Operational taxonomy for assets Preserves readable naming across campaigns, ad sets, ads, and creatives
UTM parameters Tracking taxonomy Treated as infrastructure, not optional metadata
Readiness checks Pre-launch validation layer Covers account setup, creative validation, and tracking status
Rationale notes Decision log for builds and edits Documents why a structure or change was chosen
Checklist output Launch and maintenance control surface Ensures builds are created in PAUSED and reviewed before publication

Expected metadata principles

  • Every new asset should be created in PAUSED.
  • Rationales should be recorded before publishing.
  • Naming and UTM decisions should be stable and reusable.
  • Missing MCP capabilities should be explicitly flagged rather than simulated.

Meta Ads Operator Advanced Features

  • MCP-agnostic operation: works with any connected Meta Ads MCP as long as required capabilities are discoverable.
  • Paused-first build safety: prevents accidental live launches by creating new assets in PAUSED.
  • Controlled edit workflows: supports structured updates instead of untracked manual changes.
  • Readiness diagnostics: validates account setup, creative readiness, and campaign prerequisites before execution.
  • Rationale-driven operations: forces documentation of the strategy behind each build or modification.
  • Naming and UTM governance: treats tracking and naming as first-class infrastructure.
  • Capability-aware fallback handling: cleanly marks unsupported actions as out of scope when the MCP lacks a tool.
  • Openclaw Skills portability: designed to be portable and reusable across agent environments.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*