No user-submitted related servers found.
Scored across 47 tools
Several tools have overlapping purposes: create_pmax_campaign and draft_campaign both create campaigns, remove_entity and remove_keywords both delete keywords, and update_campaign overlaps with pause_entity/enable_entity for campaign status changes. The detailed descriptions help, but an agent could easily select the wrong tool for the same underlying operation.
The names are all snake_case but the verb conventions are inconsistent: create_ and draft_ are used interchangeably for the same 'draft a write' pattern, get_ and list_ both appear for read operations, and generic tools like remove_entity sit alongside specific remove_keywords/remove_geo_target. This makes the tool surface less predictable than it could be.
With 47 tools, this is far beyond the 25-tool threshold the rubric treats as too many. The server covers a broad domain, but many tools are convenience wrappers (e.g., get_campaign_performance, get_ad_performance, run_report) and the set would benefit from consolidation.
There is no tool to create an ad group, which is a core requirement for building out a Search campaign: draft_campaign creates campaigns and draft_keywords/draft_responsive_search_ad need ad groups, so the lifecycle has a critical dead end. Other gaps include no ad-copy update path and no way to create shared negative keyword lists.