cogny clianalyticsfirst 15 calls free

google tag manager scriptable from Bash.

Walk the account → container → workspace tree, list and search tags, triggers, and variables, run a GDPR privacy audit, and create or publish container versions — all from the shell over the Google Tag Manager MCP. No GTM UI clicking, no API client.

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

Start free @cogny/cli on npm

01two paths

you're a person

Auditing a container today means clicking through every tag, trigger, and variable in the GTM UI to find what fires where and whether consent is wired up. The CLI returns the whole workspace as JSON so you (or an agent) can diff it, grep it, and publish a versioned change. Connect Google Tag Manager 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 Tag Manager tool over JSON-RPC. The first 15 calls are free.

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

02tools call

real Google Tag Manager tools.

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

mcp__Google_Tag_Manager__tool_list_tags
List every tag in a workspace with its type and firing triggers.
- cogny tools call mcp__Google_Tag_Manager__tool_list_tags \ --input '{"account_id":"6139230416","container_id":"137051450","workspace_id":"5"}'
example response
```
[
  {
    "tagId": "30",
    "name": "GA4 - Custom Events",
    "type": "gaawe",
    "firingTriggerId": [
      "29"
    ]
  },
  {
    "tagId": "12",
    "name": "GA4 Config",
    "type": "gaawc",
    "firingTriggerId": [
      "2147479553"
    ]
  }
]
```
mcp__Google_Tag_Manager__tool_audit_container_privacy
Flag tracking tags, cookie variables, and missing consent triggers.
- cogny tools call mcp__Google_Tag_Manager__tool_audit_container_privacy \ --input '{"account_id":"6139230416","container_id":"137051450","workspace_id":"5"}'
example response
```
{
  "tracking_tags": [
    {
      "name": "Meta Pixel",
      "type": "html",
      "has_consent_trigger": false
    }
  ],
  "cookie_variables": [
    "_fbp",
    "_ga"
  ],
  "recommendations": [
    "Add a consent-mode trigger to \"Meta Pixel\" before it fires."
  ]
}
```
mcp__Google_Tag_Manager__tool_create_version
Snapshot the workspace into a publishable container version.
- cogny tools call mcp__Google_Tag_Manager__tool_create_version \ --input '{"account_id":"6139230416","container_id":"137051450","workspace_id":"5","name":"Add GA4 lead event tag","notes":"Wires generate_lead to GA4."}'
example response
```
{
  "containerVersionId": "47",
  "name": "Add GA4 lead event tag",
  "tagCount": 14
}
```

03tools list

the rest of the surface.

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

mcp__Google_Tag_Manager__tool_list_accounts
mcp__Google_Tag_Manager__tool_list_containers
mcp__Google_Tag_Manager__tool_get_container_snippet
mcp__Google_Tag_Manager__tool_list_triggers
mcp__Google_Tag_Manager__tool_list_variables
mcp__Google_Tag_Manager__tool_search_tags
mcp__Google_Tag_Manager__tool_create_tag
mcp__Google_Tag_Manager__tool_create_trigger
mcp__Google_Tag_Manager__tool_publish_version

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 Tag Manager CLI?: No — it is the Cogny CLI calling the Google Tag Manager MCP over the cogny-mcp-proxy. You connect Google once in Cogny and then read or edit containers from Bash with no tagmanager API client to wire up.
Can it actually publish, or only read the container?: Both. Read tools list accounts, containers, workspaces, tags, triggers, and variables. Write tools create/update/delete tags, triggers, and variables, then tool_create_version snapshots the workspace and tool_publish_version makes it live (subject to the connected account’s GTM publish permission and OAuth scope).
Does it help with GDPR compliance?: tool_audit_container_privacy scans a workspace for third-party tracking tags, cookie variables, and tags firing without a consent trigger, and returns recommendations — a fast first pass before a manual review.

06related

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

google tag manager, then a verdict.

Start free All CLIs