Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hamzabellouch/agent-skills --skill google-ads-api-mcp-setupgit clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hamzabellouch/agent-skills/google-ads-api-mcp-setup)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/google-ads-api-mcp-setup"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/google-ads-api-mcp-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/google-ads-api-mcp-setup"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/google-ads-api-mcp-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00067 | $0.05778 |
| Opus 5 | $0.00034 | $0.02889 |
| Sonnet 5 | $0.00013 | $0.01156 |
| Haiku 4.5 | $0.00007 | $0.00578 |
Grade C, and why
google-ads-api-mcp-setup scanned grade C with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt install pipx && pipx ensurepath Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
After deployment, update your MCP client configuration (for example, `~/.gemini/settings.json` or Claude/Cursor config) to use the Cloud Run URL: This is a copy
100% identical to google-ads-api-mcp-setup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Ads API MCP Server Installation
This skill provides a structured setup guide to install, configure, and integrate the official open-source Google Ads Model Context Protocol (MCP) Server.
System Requirements & Compatibility (Agent Action: State Required Prerequisites)
When answering questions about installing or setting up the MCP server, you
MUST explicitly state to the user that both Python 3.12+ and pipx
are strictly required prerequisites for the installation.
[!IMPORTANT] Pre-Flight Environment Check:
- Python Runtime: Version
3.12+is strictly required.- Package Manager:
pipxmust be installed and globally accessible in the system path.- Network Connectivity: Outbound HTTPS access is required to connect to the Google Ads API endpoints (
googleads.googleapis.com) and PyPI.
⚠️ Prerequisites: Credentials Required
[!WARNING] Dependency Check: The MCP server requires the same 5 authentication credentials as a standard integration.
If you do not have your Developer Token, Client ID, Client Secret, Refresh Token, and Customer IDs yet:
- STOP executing this skill.
- Transition to the
google-ads-api-quickstartskill first to generate them, then return here.
Step 1: Validate Your Google Ads API Credentials
The Google Ads MCP Server requires the same five parameters as the standard client libraries. Before proceeding to installation, verify that you have these values secured and formatted correctly:
- Developer Token: Your unique API access key from the API Center (Manager Account).
- OAuth2 Client ID & Client Secret: Desktop Application credentials from the Google Cloud Console.
- OAuth2 Refresh Token: The long-lived token generated via the OAuth consent flow.
- Client Customer ID: The 10-digit target Google Ads account ID.
-
[!IMPORTANT]
-
Format: Must contain digits only, no hyphens (e.g.,
1234567890, NOT123-456-7890).
-
- Login Customer ID (Required for MCC Hierarchies): The 10-digit Manager Account (MCC) ID.
- Format: Digits only, no hyphens (e.g.,
9876543210). - Note: Essential if your OAuth credentials belong to a Manager Account administrator rather than directly to the client account.
- Format: Digits only, no hyphens (e.g.,
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 463 lines · 67 tokens per session scan C 7cfbc44bea4e
google-ads-api-mcp-setup is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 5,778 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (asks for root, reads agent configuration directories). It is 100% identical to google-ads-api-mcp-setup, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
spec-implement
Orchestrate parallel implementation of a feature specification by dispatching coder agents batch-by-batch with code review gates between batches. Use this skill when the user says "implement this feature", "start implementing", "run the spec", "execute the plan", "continue implementing", or wants to begin coding a…
spec-create
Create a structured feature specification with self-contained task files organized into parallel execution batches. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture…
spec-ship
Push the current branch to GitHub and create a pull request. Use this skill when the user says "ship it", "ship this", "push to github", "create a pr", "open a pull request", "send for review", "get this reviewed", or wants to push their work and open a PR. Also use when the user says "/spec-ship" (or their host's…
spec-checkpoint
Create a comprehensive checkpoint commit with detailed analysis of all changes. Use this skill when the user says "checkpoint", "commit everything", "save my progress", "create a commit", or wants to stage and commit all current changes with a well-crafted message. Also use when the user says "/spec-checkpoint" (or…
generative-seo
Run an evidence-based SEO + GEO (Generative Engine Optimization) program for ANY website or product codebase — auditing technical SEO, writing or retrofitting content so it gets cited by ChatGPT/Perplexity/AI Overviews, tracking AI-citation visibility, refreshing competitor research, and drafting distribution posts.…
spec-verify
Verify a completed feature spec by driving the real running app — not just lint/typecheck/build — and checking off every acceptance criterion from its specs/{feature}/ folder one by one. Use this after /spec-implement finishes a spec, when the user says "test this end to end", "verify this feature actually works"…