AI & automation
Tools that let an AI assistant run marketing accounts
We built the tools that let an AI assistant work inside a company's ad, email, and analytics accounts, within set limits, instead of a person logging into each one by hand.
Five servers with 354 tools we wrote, plus an adapted open-source call-tracking server, so an AI assistant can work directly in a company's advertising, email, and analytics accounts instead of a person clicking through six dashboards. The Google Ads server is in regular use on live campaigns.
- Google Ads tools
- Meta tools
- Email tools
- Analytics tools
- Guardrails
- TypeScript
- Model Context Protocol
- Zod
- Google Ads API
- Meta Marketing API
- Mailchimp API
- GA4
Before
The growth team ran advertising, email, call tracking, and analytics for a multi-location operator across half a dozen platforms, each with its own console and its own busywork. A routine change meant logging into several tools and clicking through the same steps by hand. They wanted to run the work through an AI assistant instead, but an assistant is only as capable as the tools it can safely call. We built that tool layer.
What made it hard
Six platforms with completely different interfaces had to answer to one consistent, machine-callable surface.
An AI assistant cannot be handed unchecked access, so every tool needed typed, validated inputs.
Coverage had to be broad enough to actually run campaigns, not just read reports, which meant a large and carefully structured set of tools.
What we built
Built five servers for Google Ads (186 tools), Meta (139), Mailchimp (15), GA4 (7), and Monday (7), and adapted an open-source CallRail server (67 tools) to run alongside them.
Covered real operating work, not just reports: campaigns, ad groups, keywords, budgets, bidding, audiences, assets, and reporting on both ad platforms.
Gave every tool typed, validated inputs, so the assistant works inside defined limits.
Used the Google Ads server on live work: building the fall 2026 campaign, fixing bidding in September 2026, and pulling the account history for a full campaign ranking.
Results
421 in total with the adapted call-tracking server, most of them in the two ad platforms, where campaign, budget, and audience work happens.
Google Ads, Meta, Mailchimp, GA4, Monday, and CallRail answer to one consistent interface instead of six separate consoles.
The Google Ads server built the fall 2026 campaign and made the September 2026 bidding fixes on the live account.
Where it stands
In use. The Google Ads server handles campaign builds and fixes; the other servers are built and on standby.
