meta-ads-mcp 0.2.2__tar.gz → 0.2.4__tar.gz

meta_ads_mcp-0.2.4/META_API_NOTES.md

@@ -0,0 +1,28 @@
+# Meta Ads API Notes and Limitations
+
+## Frequency Cap Visibility
+The Meta Marketing API has some limitations regarding frequency cap visibility:
+
+1. **Optimization Goal Dependency**: Frequency cap settings (`frequency_control_specs`) are only visible in API responses for ad sets where the optimization goal is set to REACH. For other optimization goals (like LINK_CLICKS, CONVERSIONS, etc.), the frequency caps will still work but won't be visible through the API.
+
+2. **Verifying Frequency Caps**: Since frequency caps may not be directly visible, you can verify they're working by monitoring:
+   - The frequency metric in ad insights
+   - The ratio between reach and impressions over time
+   - The actual frequency cap behavior in the Meta Ads Manager UI
+
+## Other API Behaviors to Note
+
+1. **Field Visibility**: Some fields may not appear in API responses even when explicitly requested. This doesn't necessarily mean the field isn't set - it may just not be visible through the API.
+
+2. **Response Filtering**: The API may filter out empty or default values from responses to reduce payload size. If a field is missing from a response, it might mean:
+   - The field is not set
+   - The field has a default value
+   - The field is not applicable for the current configuration
+
+3. **Best Practices**:
+   - Always verify important changes through both the API and Meta Ads Manager UI
+   - Use insights and metrics to confirm behavioral changes when direct field access is limited
+   - Consider the optimization goal when setting up features like frequency caps
+
+## Updates and Changes
+Meta frequently updates their API behavior. These notes will be updated as we discover new limitations or changes in the API's behavior. 

{meta_ads_mcp-0.2.2 → meta_ads_mcp-0.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: meta-ads-mcp
-Version: 0.2.2
+Version: 0.2.4
 Summary: Model Calling Protocol (MCP) plugin for interacting with Meta Ads API
 Project-URL: Homepage, https://github.com/nictuku/meta-ads-mcp
 Project-URL: Bug Tracker, https://github.com/nictuku/meta-ads-mcp/issues
@@ -195,14 +195,7 @@ Add this to your `claude_desktop_config.json` to integrate with Claude in Cursor
       - `ad_id`: Meta Ads ad ID (optional, used if url is not provided)
     - Returns: Diagnostic information about image download attempts
 
-14. `mcp_meta_ads_save_ad_image_via_api`
-    - Try to save an ad image by using the Marketing API's attachment endpoints
-    - Inputs:
-      - `access_token` (optional): Meta API access token (will use cached token if not provided)
-      - `ad_id`: Meta Ads ad ID
-    - Returns: Results of attempts to save the ad image
-
-15. `mcp_meta_ads_get_login_link`
+14. `mcp_meta_ads_get_login_link`
     - Get a clickable login link for Meta Ads authentication
     - Inputs:
       - `access_token` (optional): Meta API access token (will use cached token if not provided)
@@ -227,42 +220,73 @@ The Meta Ads MCP uses the OAuth 2.0 flow designed for desktop apps. When authent
 3. Ask you to authorize the app
 4. Redirect back to the local server to extract and store the token securely
 
-### Authentication Methods
+## Troubleshooting and Logging
+
+The Meta Ads MCP includes a comprehensive logging system to help troubleshoot issues:
 
-There are two ways to authenticate with the Meta Ads API:
+### Log Location
 
-1. **LLM/MCP Interface Authentication** (Recommended)
-   
-   When using the Meta Ads MCP through an LLM interface (like Claude), simply use any Meta Ads function. If you're not authenticated, the system will automatically provide a clickable Markdown link to complete the authentication flow.
+Log files are stored in a platform-specific location:
 
-   ```
-   [Click here to authenticate with Meta Ads API](https://www.facebook.com/dialog/oauth?...)
-   ```
+- **macOS**: `~/Library/Application Support/meta-ads-mcp/meta_ads_debug.log`
+- **Windows**: `%APPDATA%\meta-ads-mcp\meta_ads_debug.log` 
+- **Linux**: `~/.config/meta-ads-mcp/meta_ads_debug.log`
 
-   Just click the link, complete the authorization in your browser, and the token will be automatically captured and stored.
+### Common Issues
 
-2. **Command Line Authentication**
+#### App ID Issues
 
-   You can authenticate directly from the command line:
+If you encounter errors like `(#200) Provide valid app ID`, check the following:
 
-   ```bash
-   uvx meta-ads-mcp --login --app-id YOUR_APP_ID
-   ```
+1. Ensure you've set up a Meta Developer App correctly
+2. Verify that you're passing the correct App ID using one of these methods:
+   - Set the `META_APP_ID` environment variable: `export META_APP_ID=your_app_id`
+   - Pass it as a command-line argument: `meta-ads-mcp --app-id your_app_id`
 
-### Token Caching
+#### Authentication Errors
+
+Authentication errors can be tracked in the log file. Check for:
+- Token expiration issues
+- App permission problems
+- Connection errors
+
+### Debugging Command
+
+For specific image download issues, use the built-in diagnostic tool:
+
+```python
+# Using direct tool call
+mcp_meta_ads_debug_image_download(ad_id="your_ad_id")
+```
+
+This will give you detailed information about the download process and potential issues.
+
+## Running with Different App IDs
+
+If you need to use different Meta App IDs for different purposes:
+
+```bash
+# Using environment variable
+export META_APP_ID=your_app_id
+uvx meta-ads-mcp
+
+# Or using command line argument
+uvx meta-ads-mcp --app-id=your_app_id
+```
 
-Tokens are cached in a platform-specific secure location:
-- Windows: `%APPDATA%\meta-ads-mcp\token_cache.json`
-- macOS: `~/Library/Application Support/meta-ads-mcp/token_cache.json`
-- Linux: `~/.config/meta-ads-mcp/token_cache.json`
+## Privacy and Security
 
-You do not need to provide your access token for each command; it will be automatically retrieved from the cache.
+The Meta Ads MCP follows security best practices:
 
-## Environment Variables
+1. Tokens are cached in a platform-specific secure location:
+   - Windows: `%APPDATA%\meta-ads-mcp\token_cache.json`
+   - macOS: `~/Library/Application Support/meta-ads-mcp/token_cache.json`
+   - Linux: `~/.config/meta-ads-mcp/token_cache.json`
 
-You can set the following environment variables instead of passing them as arguments:
+2. You do not need to provide your access token for each command; it will be automatically retrieved from the cache.
 
-- `META_APP_ID`: Your Meta App ID (Client ID)
+3. You can set the following environment variables instead of passing them as arguments:
+   - `META_APP_ID`: Your Meta App ID (Client ID)
 
 ## Testing
 

{meta_ads_mcp-0.2.2 → meta_ads_mcp-0.2.4}/README.md

@@ -174,14 +174,7 @@ Add this to your `claude_desktop_config.json` to integrate with Claude in Cursor
       - `ad_id`: Meta Ads ad ID (optional, used if url is not provided)
     - Returns: Diagnostic information about image download attempts
 
-14. `mcp_meta_ads_save_ad_image_via_api`
-    - Try to save an ad image by using the Marketing API's attachment endpoints
-    - Inputs:
-      - `access_token` (optional): Meta API access token (will use cached token if not provided)
-      - `ad_id`: Meta Ads ad ID
-    - Returns: Results of attempts to save the ad image
-
-15. `mcp_meta_ads_get_login_link`
+14. `mcp_meta_ads_get_login_link`
     - Get a clickable login link for Meta Ads authentication
     - Inputs:
       - `access_token` (optional): Meta API access token (will use cached token if not provided)
@@ -206,42 +199,73 @@ The Meta Ads MCP uses the OAuth 2.0 flow designed for desktop apps. When authent
 3. Ask you to authorize the app
 4. Redirect back to the local server to extract and store the token securely
 
-### Authentication Methods
+## Troubleshooting and Logging
+
+The Meta Ads MCP includes a comprehensive logging system to help troubleshoot issues:
 
-There are two ways to authenticate with the Meta Ads API:
+### Log Location
 
-1. **LLM/MCP Interface Authentication** (Recommended)
-   
-   When using the Meta Ads MCP through an LLM interface (like Claude), simply use any Meta Ads function. If you're not authenticated, the system will automatically provide a clickable Markdown link to complete the authentication flow.
+Log files are stored in a platform-specific location:
 
-   ```
-   [Click here to authenticate with Meta Ads API](https://www.facebook.com/dialog/oauth?...)
-   ```
+- **macOS**: `~/Library/Application Support/meta-ads-mcp/meta_ads_debug.log`
+- **Windows**: `%APPDATA%\meta-ads-mcp\meta_ads_debug.log` 
+- **Linux**: `~/.config/meta-ads-mcp/meta_ads_debug.log`
 
-   Just click the link, complete the authorization in your browser, and the token will be automatically captured and stored.
+### Common Issues
 
-2. **Command Line Authentication**
+#### App ID Issues
 
-   You can authenticate directly from the command line:
+If you encounter errors like `(#200) Provide valid app ID`, check the following:
 
-   ```bash
-   uvx meta-ads-mcp --login --app-id YOUR_APP_ID
-   ```
+1. Ensure you've set up a Meta Developer App correctly
+2. Verify that you're passing the correct App ID using one of these methods:
+   - Set the `META_APP_ID` environment variable: `export META_APP_ID=your_app_id`
+   - Pass it as a command-line argument: `meta-ads-mcp --app-id your_app_id`
 
-### Token Caching
+#### Authentication Errors
+
+Authentication errors can be tracked in the log file. Check for:
+- Token expiration issues
+- App permission problems
+- Connection errors
+
+### Debugging Command
+
+For specific image download issues, use the built-in diagnostic tool:
+
+```python
+# Using direct tool call
+mcp_meta_ads_debug_image_download(ad_id="your_ad_id")
+```
+
+This will give you detailed information about the download process and potential issues.
+
+## Running with Different App IDs
+
+If you need to use different Meta App IDs for different purposes:
+
+```bash
+# Using environment variable
+export META_APP_ID=your_app_id
+uvx meta-ads-mcp
+
+# Or using command line argument
+uvx meta-ads-mcp --app-id=your_app_id
+```
 
-Tokens are cached in a platform-specific secure location:
-- Windows: `%APPDATA%\meta-ads-mcp\token_cache.json`
-- macOS: `~/Library/Application Support/meta-ads-mcp/token_cache.json`
-- Linux: `~/.config/meta-ads-mcp/token_cache.json`
+## Privacy and Security
 
-You do not need to provide your access token for each command; it will be automatically retrieved from the cache.
+The Meta Ads MCP follows security best practices:
 
-## Environment Variables
+1. Tokens are cached in a platform-specific secure location:
+   - Windows: `%APPDATA%\meta-ads-mcp\token_cache.json`
+   - macOS: `~/Library/Application Support/meta-ads-mcp/token_cache.json`
+   - Linux: `~/.config/meta-ads-mcp/token_cache.json`
 
-You can set the following environment variables instead of passing them as arguments:
+2. You do not need to provide your access token for each command; it will be automatically retrieved from the cache.
 
-- `META_APP_ID`: Your Meta App ID (Client ID)
+3. You can set the following environment variables instead of passing them as arguments:
+   - `META_APP_ID`: Your Meta App ID (Client ID)
 
 ## Testing
 

{meta_ads_mcp-0.2.2 → meta_ads_mcp-0.2.4}/future_improvements.md

@@ -1,8 +1,12 @@
 # Future Improvements for Meta Ads MCP
 
-## Planned Improvement: Refactored meta_ads_generated.py
+## Note about Meta Ads development work
 
-This file currently has too much code and it needs to be split into a small number of modules.
+If you update the MCP server code, please note that *I* have to restart the MCP server. After the server code is changed, ask me to restart it and then proceed with your testing after I confirm it's restarted.
+
+## Access token should remain internal only
+
+Don't share it ever with the LLM, only update the auth cache.
 
 ## Planned Improvement: Ad Set Update Confirmation Flow
 

{meta_ads_mcp-0.2.2 → meta_ads_mcp-0.2.4}/meta_ads_mcp/__init__.py

@@ -7,9 +7,27 @@ with the Claude LLM.
 
 from meta_ads_mcp.core.server import main
 
-__version__ = "0.2.2"
+__version__ = "0.2.4"
 
-__all__ = ["main"]
+__all__ = [
+    'get_ad_accounts',
+    'get_account_info',
+    'get_campaigns',
+    'get_campaign_details',
+    'create_campaign',
+    'get_adsets',
+    'get_adset_details',
+    'update_adset',
+    'get_ads',
+    'get_ad_details',
+    'get_ad_creatives',
+    'get_ad_image',
+    'get_insights',
+    'debug_image_download',
+    'get_login_link',
+    'login_cli',
+    'main'
+]
 
 # Import key functions to make them available at package level
 from .core import (
@@ -27,9 +45,9 @@ from .core import (
     get_ad_image,
     get_insights,
     debug_image_download,
-    save_ad_image_via_api,
     get_login_link,
     login_cli,
+    main
 )
 
 # Define a main function to be used as a package entry point

meta_ads_mcp-0.2.4/meta_ads_mcp/__main__.py

@@ -0,0 +1,10 @@
+"""
+Meta Ads MCP - Main Entry Point
+
+This module allows the package to be executed directly via `python -m meta_ads_mcp`
+"""
+
+from meta_ads_mcp.core.server import main
+
+if __name__ == "__main__":
+    main()