Related Servers

Each tool targets a distinct resource or action: account details, balance, child accounts (with/without balances), transfers, advertisers, contracts, campaigns, groups, creatives, budget/price changes, stats per entity, user management, and a raw request fallback. Even the three stats tools are clearly separated by entity level and documented. The only potential confusion is list_child_accounts vs list_child_accounts_with_balances, but the descriptions clarify the difference.

All tool names follow a consistent snake_case verb_noun pattern: get_*, list_*, create_*, change_*, transfer_*, set_*, delete_*, add_*, and the stats tools use object_stats (campaign_stats, group_stats, creative_stats). The conventions are uniform and predictable, with no mixing of camelCase or inconsistent verb styles.

25 tools is at the upper boundary of the 'borderline heavy' range. The scope covers a broad Ad platform API including accounts, child accounts, transfers, advertisers, contracts, campaigns, groups, creatives, stats, and user management, which justifies many tools. However, the presence of raw_request as a catch-all suggests that some endpoints could be consolidated or that the dedicated tool set is more expansive than necessary, pushing it slightly above the ideal 15-tool sweet spot.

The server is heavily read-oriented: campaigns, groups, and creatives are only listable; there are no create, update, pause, resume, delete, or moderation operations for these core ad objects. Only group budget and price can be modified. This leaves significant gaps in managing the full advertising lifecycle (e.g., creating campaigns or creatives, pausing ads), which agents would need to work around. The raw_request tool can access write endpoints, but without client-side validation, it is a risky workaround rather than a proper part of the surface.