openads-ai 0.2.10 → 0.2.14

package/dist/cli.js

@@ -93,6 +93,9 @@ function buildSystemPrompt(config) {
         '- You have direct, live access to Google Ads, Meta Ads, and Google Analytics 4 (GA4) via custom Model Context Protocol (MCP) server tools.',
         '- Whenever the user asks to check campaigns, review metrics, fetch performance data, or analyze active ads, you MUST use the corresponding MCP server tools to query the live platforms.',
         '- NEVER search the local file system, run grep/ripgrep, check Git logs, or read codebase files to search for ad campaign data. The active folder is just the application source code — it contains zero campaign metrics. Campaign data comes ONLY from querying your active MCP server tools.',
+        '- To fetch Meta campaign data: ALWAYS call `get_ad_accounts()` first (takes no parameters) to retrieve the active account ID (e.g., `act_123456789`). Then call `list_campaigns(account_id)` to list campaigns and retrieve active campaign IDs. Finally, call `get_campaign_performance` or `get_insights` using the retrieved IDs. Never guess or omit `object_id` when calling performance tools.',
+        '- You are a highly proactive, self-starting digital marketer. When the user asks to check campaigns or fetch reports, DO NOT ask for permission or prompt them for campaign IDs. IMMEDIATELY call your read-only discovery tools (`get_ad_accounts` followed by `list_campaigns`) to fetch the active IDs and retrieve the data yourself. Be proactive and deliver results instantly rather than hesitating or asking redundant confirmation questions.',
+        '- ANTI-LOOP SAFETY RULE: Once a tool (like `get_ad_accounts`) successfully returns its data, NEVER call it again in the same turn. Proceed immediately to the next logical step (e.g. calling `list_campaigns` or `get_campaign_performance`). If you repeat the exact same tool call consecutively, your connection will be flagged. Always move forward and progress through the tool chain.',
     ];
     if (isLaunchMode) {
         parts.push('YOU ARE OPERATING IN LAUNCH MODE (READ-WRITE).', 'You are authorized to execute active write modifications on ad accounts (e.g. pausing campaigns, scaling bids, altering daily budgets, creating ads).', 'CRITICAL SAFETY RULE: For any write operation, you MUST generate a clear visual preview card outlining the exact changes and ask the user for explicit confirmation (Y/N) before executing. NEVER make active changes without their explicit confirmation.');

package/dist/mcp-extension.js

@@ -4,6 +4,22 @@ import { hasGlobalRtk } from "./token-optimizer.js";
 import fs from "fs";
 import path from "path";
 import os from "os";
+// ─── Essential Campaign Analysis & Audit Tools ──────────────────────
+// Filtering down from 39 tools to 11 essential campaign performance tools
+// massively optimizes local LLM context, prevents tool confusion, and breaks repeating loops.
+const ESSENTIAL_META_TOOLS = new Set([
+    "get_ad_accounts",
+    "list_campaigns",
+    "get_campaign",
+    "get_campaign_performance",
+    "get_insights",
+    "list_ad_sets",
+    "list_ads",
+    "get_creative_performance",
+    "pause_campaign",
+    "resume_campaign",
+    "update_campaign"
+]);
 export default async function (pi) {
     const configDir = path.join(os.homedir(), '.openads');
     const configPath = path.join(configDir, 'openads.config.json');
@@ -27,8 +43,9 @@ export default async function (pi) {
             const googleTransport = new StdioClientTransport({
                 command,
                 args,
+                stderr: "ignore"
             });
-            const googleClient = new Client({ name: "openads-google-ads-client", version: "0.2.9" }, { capabilities: {} });
+            const googleClient = new Client({ name: "openads-google-ads-client", version: "0.2.14" }, { capabilities: {} });
             await googleClient.connect(googleTransport);
             clients.push({ name: "google-ads", client: googleClient });
         }
@@ -48,9 +65,10 @@ export default async function (pi) {
                 env: {
                     ...process.env,
                     "META_ACCESS_TOKEN": config.metaToken
-                }
+                },
+                stderr: "ignore"
             });
-            const metaClient = new Client({ name: "openads-meta-ads-client", version: "0.2.9" }, { capabilities: {} });
+            const metaClient = new Client({ name: "openads-meta-ads-client", version: "0.2.14" }, { capabilities: {} });
             await metaClient.connect(metaTransport);
             clients.push({ name: "meta-ads", client: metaClient });
         }
@@ -63,6 +81,10 @@ export default async function (pi) {
         try {
             const toolsResult = await client.listTools();
             for (const tool of toolsResult.tools) {
+                // Filter out advanced/OAuth/developer tools for Meta Ads to keep the LLM context extremely clean
+                if (serverName === "meta-ads" && !ESSENTIAL_META_TOOLS.has(tool.name)) {
+                    continue;
+                }
                 pi.registerTool({
                     name: tool.name,
                     label: tool.name.replace(/_/g, ' ').replace(/\b\w/g, c => c.toUpperCase()),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openads-ai",
-  "version": "0.2.10",
+  "version": "0.2.14",
   "description": "Open-source AI command center for digital marketers. Audit campaigns, write ad copy, and build strategies — from your terminal.",
   "main": "dist/cli.js",
   "bin": {

package/skills/ads/meta-ads.md

@@ -41,5 +41,15 @@ Read `product-marketing.md` first to understand the product context.
 
 ---
 
-## MCP Tools to Use
-If Meta Ads MCP is connected, you can pull campaign insights, ad sets, and ad creative performance. Ensure you review the performance to provide data-driven recommendations.
+## MCP Tools to Use & Execution Sequence
+
+When Meta Ads MCP is connected, you must follow this exact sequence to retrieve campaign data and avoid validation errors:
+
+1. **Discover Ad Accounts**: First, call `get_ad_accounts()` (no parameters required) to get the user's connected ad accounts and retrieve their `account_id` (e.g., `act_123456789`).
+2. **List Campaigns**: Once you have the `account_id`, call `list_campaigns(account_id: "act_YOUR_ACCOUNT_ID")` to get a list of active and inactive campaigns with their names and `id`s.
+3. **Fetch Performance & Insights**:
+   - To check overall campaign metrics, call `get_campaign_performance(object_id: "YOUR_CAMPAIGN_ID", level: "CAMPAIGN")`.
+   - Or to check account-wide metrics, call `get_campaign_performance(object_id: "act_YOUR_ACCOUNT_ID", level: "AD_ACCOUNT")`.
+   - To retrieve detailed ads/adset insights, breakdowns, or custom metrics, call `get_insights(object_id: "YOUR_CAMPAIGN_ID", level: "CAMPAIGN")`.
+
+**CRITICAL RULE**: Never guess campaign IDs or call `get_campaign_performance` or `get_insights` without an `object_id`. Always query `get_ad_accounts()` first, then `list_campaigns()`, and finally fetch performance.