No user-submitted related servers found.
Scored across 3 tools
Each tool has a clearly distinct purpose: listing customer IDs, retrieving metadata for a resource, and executing a search query. There is no overlap or ambiguity between them.
All tool names use snake_case with a resource prefix followed by an action (customers_list_accessible_customers, metadata_get_resource_metadata, search_search). The pattern is mostly consistent, though search_search is slightly redundant and the action structures vary a bit.
Three tools is on the low side but reasonable for a focused read-only server that uses a generic search tool to cover many query scenarios. Each tool earns its place, though the surface feels minimal for the breadth of Google Ads.
The tool set covers read-only discovery and querying well, but lacks any create, update, or delete operations. For a Google Ads management server, this is a notable gap, even though the search tool can handle many read queries.