You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 34a8265
Browse filesBrowse the repository at this point in the historyBrowse files
Update README.md to correct function names and improve parameter descriptions for Meta Ads API functions. Adjusted numbering for functions to reflect changes in the list order.
Copy file name to clipboardExpand all lines: README.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -346,16 +346,16 @@ For local installation configuration, authentication options, and advanced techn
346
346
- `access_token` (optional): Meta API access token (will use cached token if not provided)
347
347
- Returns: A clickable resource link for Meta authentication
348
348
349
-
22. `mcp_meta-ads_create_budget_schedule`
350
-
- Create a budget schedule for a Meta Ads campaign.
349
+
22. `mcp_meta_ads_create_budget_schedule`
350
+
- Create a budget schedule for a Meta Ads campaign
351
351
- Inputs:
352
-
- `campaign_id`: Meta Ads campaign ID.
353
-
- `budget_value`: Amount of budget increase.
354
-
- `budget_value_type`: Type of budget value ("ABSOLUTE" or "MULTIPLIER").
355
-
- `time_start`: Unix timestamp for when the high demand period should start.
356
-
- `time_end`: Unix timestamp for when the high demand period should end.
357
-
- `access_token` (optional): Meta API access token.
358
-
- Returns: JSON string with the ID of the created budget schedule or an error message.
352
+
- `campaign_id`: Meta Ads campaign ID
353
+
- `budget_value`: Amount of budget increase
354
+
- `budget_value_type`: Type of budget value ("ABSOLUTE" or "MULTIPLIER")
355
+
- `time_start`: Unix timestamp for when the high demand period should start
356
+
- `time_end`: Unix timestamp for when the high demand period should end
357
+
- `access_token` (optional): Meta API access token
358
+
- Returns: JSON string with the ID of the created budget schedule or an error message
359
359
360
360
23. `mcp_meta_ads_search_interests`
361
361
- Search for interest targeting options by keyword
@@ -373,30 +373,30 @@ For local installation configuration, authentication options, and advanced techn
373
373
- `limit`: Maximum number of suggestions to return (default: 25)
374
374
- Returns: Suggested interests with id, name, audience_size, and description fields
375
375
376
-
24. `mcp_meta_ads_validate_interests`
376
+
25. `mcp_meta_ads_validate_interests`
377
377
- Validate interest names or IDs for targeting
378
378
- Inputs:
379
379
- `access_token` (optional): Meta API access token (will use cached token if not provided)
380
380
- `interest_list`: List of interest names to validate (e.g., ["Japan", "Basketball"])
381
381
- `interest_fbid_list`: List of interest IDs to validate (e.g., ["6003700426513"])
382
382
- Returns: Validation results showing valid status and audience_size for each interest
383
383
384
-
25. `mcp_meta_ads_search_behaviors`
384
+
26. `mcp_meta_ads_search_behaviors`
385
385
- Get all available behavior targeting options
386
386
- Inputs:
387
387
- `access_token` (optional): Meta API access token (will use cached token if not provided)
388
388
- `limit`: Maximum number of results to return (default: 50)
389
389
- Returns: Behavior targeting options with id, name, audience_size bounds, path, and description
390
390
391
-
26. `mcp_meta_ads_search_demographics`
391
+
27. `mcp_meta_ads_search_demographics`
392
392
- Get demographic targeting options
393
393
- Inputs:
394
394
- `access_token` (optional): Meta API access token (will use cached token if not provided)
395
395
- `demographic_class`: Type of demographics ('demographics', 'life_events', 'industries', 'income', 'family_statuses', 'user_device', 'user_os')
396
396
- `limit`: Maximum number of results to return (default: 50)
397
397
- Returns: Demographic targeting options with id, name, audience_size bounds, path, and description
398
398
399
-
27. `mcp_meta_ads_search_geo_locations`
399
+
28. `mcp_meta_ads_search_geo_locations`
400
400
- Search for geographic targeting locations
401
401
- Inputs:
402
402
- `access_token` (optional): Meta API access token (will use cached token if not provided)
@@ -405,7 +405,7 @@ For local installation configuration, authentication options, and advanced techn
405
405
- `limit`: Maximum number of results to return (default: 25)
406
406
- Returns: Location data with key, name, type, and geographic hierarchy information
407
407
408
-
28. `mcp_meta_ads_search` (Enhanced)
408
+
29. `mcp_meta_ads_search` (Enhanced)
409
409
- Generic search across accounts, campaigns, ads, and pages
410
410
- Automatically includes page searching when query mentions "page" or "pages"
411
411
- Inputs:
@@ -454,7 +454,7 @@ The easiest way to avoid any setup issues is to **[🎯 use our Remote MCP inste
454
454
For comprehensive troubleshooting, debugging, and local installation issues, see our **[Local Installation Guide](LOCAL_INSTALLATION.md)** which includes:
0 commit comments