Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MCP Google Ads

PYPI · MCP-GOOGLE-ADS-MULTI

Multi-account Google Ads MCP: campaigns, keywords, search terms, and ad performance.

−2 this week 82 Trust /100

Last scanned (3 hours ago)

Scores higher than 84% of PyPI servers

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 38 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 678 tokens (~67/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 68% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Provenance: unverified → fail ▼ security
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 29 Oct 26 0
    • Provenance: fail → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 25 Oct 26 +15
    • Provenance: unverified → fail ▼ security
    • Malware scan: unverified → pass ▲ security
  • 24 Oct 26 0
    • Provenance: fail → unverified ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/mcp-google-ads-multi@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 38 packages
Packages resolved 38
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~678 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_periods ~89

Compare performance between two date ranges.

NameTypeReqDescription
account––Named account from config
breakdownstring–'campaign' or 'account' level comparison
customer_idstringyesGoogle Ads customer ID
period1_endstringyes–
period1_startstringyes–
period2_endstringyes–
period2_startstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_account_summary ~86

Get top-level spend and conversion totals for an account.

NameTypeReqDescription
account––Named account from config (uses default if omitted)
customer_idstringyesGoogle Ads customer ID (e.g. '123-456-7890' or '1234567890')
end_datestringyesYYYY-MM-DD
start_datestringyesYYYY-MM-DD

Structured output declared, but exposes no named fields.

No examples provided.

get_ad_performance ~88

Get ad-level performance (headlines, descriptions, CTR, conversions).

NameTypeReqDescription
account––Named account from config
campaign_id––Filter to specific campaign (optional)
customer_idstringyesGoogle Ads customer ID
end_datestringyes–
row_limitinteger–Ads to return (default 25)
start_datestringyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

get_campaign_performance ~76

Get campaign performance metrics for a date range.

NameTypeReqDescription
account––Named account from config
campaign_id––Filter to a specific campaign ID (optional)
customer_idstringyesGoogle Ads customer ID
end_datestringyesYYYY-MM-DD
start_datestringyesYYYY-MM-DD
NameTypeReqDescription
resultarrayyes–

No examples provided.

get_keyword_performance ~90

Get keyword-level performance including quality scores.

NameTypeReqDescription
account––Named account from config
campaign_id––Filter to a specific campaign (optional)
customer_idstringyesGoogle Ads customer ID
end_datestringyes–
row_limitinteger–Number of keywords to return (default 50, max 1000)
start_datestringyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

list_accounts ~21

List all configured Google Ads accounts and which is the current default.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_campaigns ~61

List campaigns for an account.

NameTypeReqDescription
account––Named account from config
customer_idstringyesGoogle Ads customer ID
status––Filter by status — ENABLED, PAUSED, REMOVED (default: ENABLED and PAUSED)
NameTypeReqDescription
resultarrayyes–

No examples provided.

list_customers ~50

List all accessible Google Ads customer accounts. If customer_id is provided, lists child accounts under that MCC. Otherwise lists all accessible accounts for this login.

NameTypeReqDescription
account–––
customer_id–––
NameTypeReqDescription
resultarrayyes–

No examples provided.

search_terms_report ~87

Get actual search terms that triggered your ads.

NameTypeReqDescription
account––Named account from config
campaign_id––Filter to specific campaign (optional)
customer_idstringyesGoogle Ads customer ID
end_datestringyes–
row_limitinteger–Rows to return (default 50, max 1000)
start_datestringyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

set_default_account ~30

Set the default account used when no account is specified in other tools.

NameTypeReqDescription
accountstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the MCP Google Ads server?

MCP Google Ads runs locally as a PyPI package, launched with uvx mcp-google-ads-multi. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-google-ads-multi

# add to Claude Code
claude mcp add ayo-fam-mcp-google-ads -- uvx mcp-google-ads-multi
Common questions

What is the MCP Google Ads server?

MCP Google Ads is listed in the public MCP registry as io.github.Ayo-Fam/mcp-google-ads. Multi-account Google Ads MCP: campaigns, keywords, search terms, and ad performance. This page covers its PyPI package (mcp-google-ads-multi).

Is the MCP Google Ads server safe to use?

MCP Google Ads scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MCP Google Ads server expose?

MCP Google Ads exposes 10 tools: list_accounts, set_default_account, list_customers, get_account_summary, list_campaigns, and 5 more. Their descriptions and schemas cost roughly 678 tokens of context every time the server is loaded.

Is the MCP Google Ads server still maintained?

MCP Google Ads is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the MCP Google Ads server under?

MCP Google Ads declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.