No user-submitted related servers found.
Scored across 42 tools
Most tools map cleanly to distinct resources (campaigns, adsets, ads, creatives, targeting, insights). A few overlapping pairs exist—get_ad_creatives vs get_creative_details, get_account_pages vs search_pages_by_name, get_ad_image vs get_image_by_hash—but their descriptions clarify the intended inputs and use cases.
The dominant pattern is verb_noun (get_campaigns, create_adset, update_ad, upload_ad_image, search_interests). A few generic names (search, fetch) and slight deviations (get_image_by_hash not following get_<resource>) break the pattern, but the overall structure is predictable and readable.
At 42 tools, this server exceeds the 'heavy' threshold and feels over-scoped for a single MCP server. While the Meta Ads domain is broad, many tools are narrow (e.g., compute_image_crops, create_budget_schedule) and several overlap in function, inflating the count beyond what is needed for core ad management.
The surface covers the full campaign→adset→ad→creative hierarchy with create, read, and update operations, plus insights, targeting search, page posts, and budget schedules. Notable gaps include missing delete/archive endpoints and the oddly coupled search/fetch pair, but these do not severely hamper core workflows.