MCP Tool Catalogue
These are the tools an AI assistant can call once connected to the Synaptyx MCP server. They fall into four groups: reads, analysis, Synaptyx writes, and Facebook Marketing.
Write tools are dry-run by default. They return a preview of the change unless the
assistant explicitly passes dry_run: false. Deletes additionally require a
confirmation token. This makes it safe to let an assistant propose changes you then
approve.
Reads — your tracking data
| Tool | Returns |
|---|---|
get_overview | Headline KPIs over a window |
get_daily_stats | Daily clicks/conversions/revenue series |
get_breakdown | Performance by dimension (country, device…) |
get_report | Grouped report |
get_node_stats | Stats for a specific flow node / rotator |
list_campaigns | Your campaigns |
get_campaign_flow | A campaign’s routing flow |
get_campaign_detail | Full campaign detail |
list_offers | Your offers |
list_landing_pages | Your landing pages |
get_traffic_sources | Your traffic sources |
get_geo_performance | Performance by geography |
get_offer_performance | Performance by offer |
get_budget_status | Campaign budget pacing |
get_alert_rules | Your alert rules |
get_postback_logs | Recent postback logs |
list_funnels / get_funnel_analytics | Funnels and their stage analytics |
get_sub_affiliate_report | Sub-affiliate performance |
Analysis — let the model reason
| Tool | Does |
|---|---|
get_campaign_health | A health assessment of a campaign |
get_optimization_suggestions | Concrete optimization ideas |
get_segment_analysis | Segment-level analysis |
detect_anomalies | Surfaces statistically unusual changes |
get_funnel_bottlenecks | Where a funnel is leaking |
Synaptyx writes (dry-run by default)
| Tool | Changes |
|---|---|
update_campaign_flow | Modify a campaign’s routing flow |
create_routing_rule | Add a routing rule |
update_budget | Set/adjust a campaign budget |
create_alert | Create an alert rule |
add_to_blacklist | Add an IP/UA to your blocklists |
Facebook Marketing
The MCP server also wraps the Facebook Marketing API so an assistant can manage ads alongside your tracking data.
| Group | Tools |
|---|---|
| Reads | fb_list_ad_accounts, fb_list_campaigns, fb_get_campaign, fb_list_adsets, fb_get_adset, fb_list_ads, fb_get_ad, fb_get_insights, fb_get_video_status |
| Targeting discovery | fb_search_targeting, fb_search_geo, fb_browse_targeting_categories |
| Writes (dry-run) | fb_create_campaign, fb_update_campaign, fb_scale_campaign_budget, fb_create_adset, fb_update_adset, fb_create_ad, fb_update_ad, fb_create_creative, fb_upload_image, fb_upload_video, fb_delete_object |
fb_delete_object is the most destructive tool: it requires both dry_run: false
and an explicit confirmation token before it will act.
Rate limits & auditing (recap)
- Reads: 600/min per user. Writes: 60/min per user. (Exceeding returns an error result the assistant can retry on, not an HTTP 429.)
- Every write — preview or applied — is logged to the MCP audit trail with redacted arguments, the dry-run flag, success/failure, affected IDs, and duration. Reads are not logged.