No user-submitted related servers found.
Scored across 21 tools
Each resource getter (campaigns, adsquads, ads, media, segments, etc.) targets a distinct entity, so most tools are separable. However, snapchat_get_creatives vs snapchat_list_ad_creatives vs snapchat_get_creative_elements and the three targeting tools (get_targeting, get_targeting_specs, get_targeting_options) require careful reading to avoid selection errors, and snapchat_get_entity overlaps conceptually with every per-resource getter.
Strong, readable snapchat_ prefix with a mostly uniform verb_resource structure. Minor deviations exist: snapchat_list_ad_creatives uses list_ while the other listing tools use get_ (get_campaigns, get_ads), and get_ is overloaded for both list and single-entity reads. Still largely predictable.
21 tools is in the heavy range for the scope, and many list tools share near-identical boilerplate descriptions, contributing to surface bloat. The count is defensible given the number of Snapchat entity types, but it sits at the borderline of too many.
Read coverage is genuinely thorough across all entity types plus insights, pixels, apps, and targeting. The critical gap is that the entire surface is read-only: there are no create/update/delete tools, yet snapchat_get_write_schema advertises creation/edit fields with nothing to apply them to, leaving a dead end for any mutation workflow.