cogny clipaid searchfirst 15 calls free

google ads from your shell.

Run GAQL, pull campaign reports, generate keyword ideas, and push budget or status changes to Google Ads — straight from Bash. No Ads UI, no API client, no OAuth dance. Just the Cogny CLI over the Google Ads MCP.

1. sign up, free for the first calls (uses your git email)npx @cogny/cli init --agent claude-code
2. see every Google Ads toolcogny tools list
3. call any tool from bash, no MCP wiringcogny tools call mcp__Google_Ads__tool_execute_gaql --input '{…}'

Start free @cogny/cli on npm

01two paths

you're a person

Today you log into the Google Ads UI, build a report, export CSV, and eyeball it. With the CLI you query the exact rows you want with GAQL and pipe the JSON into anything. Connect Google Ads once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.

Start Solo

you're an agent

Sign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Google Ads tool over JSON-RPC. The first 15 calls are free.

npx @cogny/cli init --agent claude-code

02tools call

real Google Ads tools.

Tool names as the Google Ads MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.

mcp__Google_Ads__tool_execute_gaql
Run any GAQL query and get rows back as JSON.
- cogny tools call mcp__Google_Ads__tool_execute_gaql \ --input '{"customer_id":"1234567890","query":"SELECT campaign.name, metrics.clicks, metrics.cost_micros FROM campaign WHERE segments.date DURING LAST_7_DAYS ORDER BY metrics.cost_micros DESC LIMIT 3"}'
example response
```
[
  {
    "campaign.name": "Brand — Exact",
    "metrics.clicks": 1842,
    "metrics.cost_micros": 412300000
  },
  {
    "campaign.name": "Competitor — Phrase",
    "metrics.clicks": 967,
    "metrics.cost_micros": 388100000
  },
  {
    "campaign.name": "Generic — Broad",
    "metrics.clicks": 2310,
    "metrics.cost_micros": 351900000
  }
]
```
mcp__Google_Ads__tool_generate_keyword_ideas
Get keyword ideas with monthly searches and competition.
- cogny tools call mcp__Google_Ads__tool_generate_keyword_ideas \ --input '{"customer_id":"1234567890","keywords":["running shoes"],"page_url":"https://example.com/shoes"}'
example response
```
{
  "results": [
    {
      "text": "trail running shoes",
      "avg_monthly_searches": 49500,
      "competition": "HIGH"
    },
    {
      "text": "best running shoes 2026",
      "avg_monthly_searches": 22200,
      "competition": "MEDIUM"
    }
  ]
}
```
mcp__Google_Ads__tool_update_campaign_status
Pause, enable, or remove a campaign.
- cogny tools call mcp__Google_Ads__tool_update_campaign_status \ --input '{"customer_id":"1234567890","campaign_id":"987654321","status":"PAUSED"}'
example response
```
{
  "resource_name": "customers/1234567890/campaigns/987654321",
  "status": "PAUSED"
}
```

03tools list

the rest of the surface.

A sample of the other Google Ads tools. Run cogny tools list --json for every tool and its input schema.

mcp__Google_Ads__tool_list_accessible_accounts
mcp__Google_Ads__tool_create_campaign
mcp__Google_Ads__tool_create_responsive_search_ad
mcp__Google_Ads__tool_add_keywords_to_ad_group
mcp__Google_Ads__tool_add_negative_keywords_to_campaign
mcp__Google_Ads__tool_create_negative_keyword_list
mcp__Google_Ads__tool_add_keywords_to_negative_keyword_list
mcp__Google_Ads__tool_update_campaign_budget
mcp__Google_Ads__tool_update_campaign_bidding_strategy
mcp__Google_Ads__tool_search_geo_targets
mcp__Google_Ads__tool_get_gaql_doc

04then a verdict

calls from a script. verdicts from cogny.

Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.

worked
Moved the number. Every measured win has a share card.
partial
Some of it did.
didn't work
On the record anyway, so it isn't proposed again.
inconclusive
Not enough data to call.

How the loop works

05questions

questions.

Is this an official Google Ads CLI?: No — it is the Cogny CLI calling the Google Ads MCP over the cogny-mcp-proxy. You authenticate once via Cogny (OAuth handled for you) and then call every tool from Bash. No google-ads.yaml, developer token, or client library to manage.
Do I need to write the Google Ads API client?: No. The proxy wraps the Google Ads API. You send GAQL or structured arguments; the CLI returns JSON. That is the whole surface.
Can my coding agent use this without MCP setup?: Yes — that is the point. `npx @cogny/cli init --agent claude-code` issues a key, then `cogny tools call mcp__Google_Ads__tool_execute_gaql --input ...` works from any shell. No /mcp wiring or restart needed.

06related

Building an agent? The full tool map for every server is one fetch: /cli/llms.txt

google ads, then a verdict.

Start free All CLIs