No user-submitted related servers found.
Scored across 34 tools
Most tools target distinct resources, but several pairs blur together: meta_get_creative_assets vs meta_get_creatives, meta_get_audience_details vs meta_get_audiences, meta_health_check vs meta_debug_token, and meta_get_study_results vs meta_interpret_experiment_results. The raw escape-hatch tools also add ambiguity about when to use them instead of specialized getters.
All tools share the meta_ prefix and snake_case, and most follow a predictable verb_noun pattern using list_ or get_. Minor exceptions like meta_health_check and the variety of verbs (interpret, validate, debug, join) keep it from being perfectly consistent.
At 34 tools, the surface is well above the typical well-scoped range and feels heavy. Several tools could be consolidated—audience list/detail, creative getters, auth checks, and raw generic tools—so the high count is not fully justified.
As a read-only Meta Ads data-access surface, it is quite thorough: accounts, campaigns, ad sets, ads, creatives, audiences, insights, experiments, assets, catalogs, and organic content are all covered. Minor gaps exist if write/management workflows are expected, and there is no dedicated single-campaign/single-ad-set getter aside from the generic meta_get_node_fields.