Meta Ads Super Manager Skill
PassAudited by VirusTotal on May 11, 2026.
Overview
Type: OpenClaw Skill Name: facebook-ads-manager-skill Version: 1.0.0 The OpenClaw AgentSkills skill bundle for Facebook Ads Manager is benign. It is meticulously designed with a strong emphasis on safety, transparency, and user control. Key indicators include explicit guardrails in `SKILL.md` and `references/safety-policy.md` that instruct the AI agent to create campaigns in `PAUSED` status by default, require explicit user confirmation for deletions or aggressive budget changes, and use only predefined tools from `references/tools-index.md`. All listed tools are legitimate Meta Ads API operations, and there is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection designed to subvert the agent's intended purpose.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken or overbroad action could change campaigns, budgets, targeting, ads, or audiences and affect business spend or delivery.
The skill coordinates write and delete tools that can modify or remove Meta Ads account objects. This is central to the stated ad-management purpose and is paired with safety instructions, but it is still high-impact.
Write: - `create_campaign` - `update_campaign` ... Write: - `delete_audience` ... Write: - `delete_object`
Require a clear plan, exact object IDs, parameter review, and explicit approval before any write/delete or budget change; keep new objects PAUSED until validated.
If connected with an overly privileged Meta account, the agent could make changes across more ad accounts or assets than intended.
The skill is intended to operate against a Meta Ads account using account identifiers and whatever delegated permissions the MCP integration provides.
Executar campanhas Meta Ads ponta a ponta... Sempre tratar `act_id` no formato `act_<id>`.
Connect only a least-privilege Meta Ads/MCP account, verify the `act_id` before actions, and avoid giving access to unrelated business accounts.
Customer or CRM identifiers could be uploaded to Meta if the user directs the workflow, creating privacy, consent, or compliance obligations.
The audience workflow can send CRM/user audience data through MCP tools to Meta for custom audience operations. This is expected for the feature, but it involves sensitive customer data.
Criar ou atualizar base CRM - `create_custom_audience` - `update_custom_audience_users`
Confirm the exact data source, audience purpose, consent basis, and minimization/hashing requirements before uploading any CRM users.
The safety of actual Meta API calls depends on the MCP server the user connects, which was not included in these artifacts.
The skill references an external MCP server/tool implementation that is not part of the instruction-only package reviewed here.
Origem: `facebook-ads-mcp-server-ts/src/tools/*.ts`
Verify the MCP server source, version, permissions, and tool behavior before connecting it to a real Meta Ads account.