{"id":"mathiaschu-google-ads-analyzer","name":"google-ads-analyzer","af_score":54.0,"security_score":71.5,"reliability_score":26.2,"what_it_does":"Provides a local MCP server that connects to the Google Ads API, exposing read tools (GAQL search, list accessible customer IDs) and additional write tools (add negative keywords, pause/enable campaigns, update campaign budgets, change bidding strategies, and pause/enable ad groups/ads) so an LLM/agent can analyze and manage Google Ads accounts.","best_when":"You want an agent connected to Google Ads that can both retrieve reporting data and perform specific write operations using Google’s official Ads API scopes/credentials.","avoid_when":"You cannot tolerate the risk of the model triggering write tools (even if unintended) or you lack guardrails, least-privilege credentials, and monitoring/auditing for changes.","last_evaluated":"2026-03-30T15:25:17.153913+00:00","has_mcp":true,"has_api":false,"auth_methods":["Google Ads API authentication via Google Application Default Credentials (ADC) or Google Ads API Python client config","Google Ads developer token (GOOGLE_ADS_DEVELOPER_TOKEN)","Optional login customer ID for manager-account access (GOOGLE_ADS_LOGIN_CUSTOMER_ID)"],"has_free_tier":false,"known_gotchas":["Write tools can materially change campaigns/budgets/bidding/keywords; agents must have guardrails/confirmation steps.","Many prompts require a customer ID; multi-customer workflows should ensure the correct customer context.","Negative keyword matching types (BROAD/PHRASE/EXACT) must be set correctly to avoid unintended keyword blocking.","Budget and bidding changes should be validated (currency/target values) before execution.","The README notes an extra header for usage data collection; ensure this is acceptable for your environment and that it does not leak sensitive info."],"error_quality":0.0}