No user-submitted related servers found.
Scored across 41 tools
Multiple tool names are nearly identical or easily confused: meta_get_creatives vs meta_get_creative_assets, meta_get_audiences vs meta_get_audience_details, and meta_get_ad_studies vs meta_get_study_results. There is also a cluster of raw/escape-hatch tools (meta_get_node_fields, meta_list_edge_raw, meta_get_insights_raw) that overlap conceptually. Descriptions help, but an agent would need to read closely to avoid misselecting.
All names share the meta_ prefix and snake_case, making them readable, but verb usage is inconsistent: meta_get_campaigns, meta_list_ad_accounts, meta_validate_query, meta_debug_token, and meta_interpret_experiment_results mix get/list/debug/validate/interpret. The list/get distinction is not applied predictably across collection endpoints.
With 41 tools, this surface is too large for a coherent MCP tool set and starts to resemble raw API exposure rather than a curated interface. The broad domain justifies many tools, but this count will slow agent selection and increase the risk of choosing the wrong endpoint.
For a read-only Meta Ads server, the coverage is exceptionally complete: account discovery, entity hierarchy, creatives, media, audiences, insights, studies, catalogs, diagnostics, and raw fallbacks are all present. The server even includes validation, preview, and health-check tools, so there are no obvious dead ends for the stated read-only purpose.