openads-ai 0.2.14 → 0.2.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/cli.js CHANGED
@@ -93,8 +93,8 @@ function buildSystemPrompt(config) {
93
93
  '- You have direct, live access to Google Ads, Meta Ads, and Google Analytics 4 (GA4) via custom Model Context Protocol (MCP) server tools.',
94
94
  '- 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.',
95
95
  '- 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.',
96
- '- 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.',
97
- '- 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.',
96
+ '- To fetch Meta campaign data: ALWAYS call `get_ad_accounts()` first (takes no parameters) to retrieve the active account ID. 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 literal IDs. Never guess or omit `object_id` when calling performance tools, and NEVER use generic placeholder tokens like `<your_account_id>` or `act_YOUR_ACCOUNT_ID` under any circumstances.',
97
+ '- You are a highly proactive, self-starting digital marketer. When the user asks to check campaigns, review metrics, or fetch performance reports, DO NOT stop at listing campaign names, and DO NOT ask for permission or prompt the user for campaign IDs. IMMEDIATELY proceed to query performance or insights (`get_campaign_performance` or `get_insights`) for the discovered active campaign IDs. Deliver a beautiful marketing summary with structured key metrics (spend, impressions, CTR, ROAS, conversions) proactively and instantly rather than hesitating or asking redundant confirmation questions.',
98
98
  '- 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.',
99
99
  ];
100
100
  if (isLaunchMode) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "openads-ai",
3
- "version": "0.2.14",
3
+ "version": "0.2.15",
4
4
  "description": "Open-source AI command center for digital marketers. Audit campaigns, write ad copy, and build strategies — from your terminal.",
5
5
  "main": "dist/cli.js",
6
6
  "bin": {
@@ -43,13 +43,23 @@ Read `product-marketing.md` first to understand the product context.
43
43
 
44
44
  ## MCP Tools to Use & Execution Sequence
45
45
 
46
- When Meta Ads MCP is connected, you must follow this exact sequence to retrieve campaign data and avoid validation errors:
46
+ When Meta Ads MCP is connected, you must follow this exact sequence to retrieve campaign performance data proactively without stopping or using placeholders:
47
47
 
48
- 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`).
49
- 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.
50
- 3. **Fetch Performance & Insights**:
51
- - To check overall campaign metrics, call `get_campaign_performance(object_id: "YOUR_CAMPAIGN_ID", level: "CAMPAIGN")`.
52
- - Or to check account-wide metrics, call `get_campaign_performance(object_id: "act_YOUR_ACCOUNT_ID", level: "AD_ACCOUNT")`.
53
- - To retrieve detailed ads/adset insights, breakdowns, or custom metrics, call `get_insights(object_id: "YOUR_CAMPAIGN_ID", level: "CAMPAIGN")`.
48
+ 1. **Discover Ad Accounts**: First, call `get_ad_accounts()` (takes no parameters) to retrieve the active account ID (e.g. `act_527976914813519`).
49
+ 2. **List Campaigns**: Call `list_campaigns(account_id: "act_527976914813519")` (using the literal account ID retrieved in Step 1) to get a list of active and inactive campaigns.
50
+ 3. **Fetch Performance & Insights**: Do NOT stop at listing the campaigns or ask for permission. Proceed immediately to retrieve performance/insights for the discovered active campaign IDs.
51
+ - For overall campaign performance metrics, call `get_campaign_performance(object_id: "YOUR_CAMPAIGN_ID", level: "CAMPAIGN")` using the literal campaign ID (e.g., `23845056436410209`).
52
+ - For detailed adset/ad level insights or breaking down statistics, call `get_insights(object_id: "YOUR_CAMPAIGN_ID", level: "CAMPAIGN")`.
53
+ 4. **Present Results**: Structure and format the retrieved insights into a beautiful marketing summary featuring spend, impressions, CTR, ROAS, and conversions.
54
54
 
55
- **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.
55
+ ### Execution Example Flow
56
+ ```mermaid
57
+ graph TD
58
+ A["get_ad_accounts()"] -->|Returns act_527976914813519| B["list_campaigns(account_id: 'act_527976914813519')"]
59
+ B -->|Returns Campaign 23845056436410209| C["get_campaign_performance(object_id: '23845056436410209')"]
60
+ C -->|Fetch Metrics Proactively| D[Format & Display Beautiful Marketing Summary]
61
+ ```
62
+
63
+ **CRITICAL RULES**:
64
+ - **NEVER** use generic placeholder strings like `<your_account_id>` or `act_YOUR_ACCOUNT_ID` in tool arguments under any circumstances. Always extract the literal IDs from previous tool outputs.
65
+ - **NEVER** stop at listing campaigns or ask the user "Would you like me to fetch performance details?"—always proactively fetch the performance/insights of the active campaigns.