adrails 0.2.3__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
adrails-0.2.3/LICENSE ADDED
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
adrails-0.2.3/NOTICE ADDED
@@ -0,0 +1,7 @@
1
+ AdRails (adsops)
2
+ Copyright 2026 The AdRails authors
3
+
4
+ This product is licensed under the Apache License, Version 2.0 (see LICENSE).
5
+ It is provided AS IS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND. Operating
6
+ advertising accounts with automated agents can spend real money; see
7
+ deploy/GUARD.md for what the spend guard can and cannot do.
adrails-0.2.3/PKG-INFO ADDED
@@ -0,0 +1,285 @@
1
+ Metadata-Version: 2.4
2
+ Name: adrails
3
+ Version: 0.2.3
4
+ Summary: AdRails: open-source Google Ads MCP server with hard spend guardrails. Agents read freely and write only through a reviewed desired-state file.
5
+ Author: adsops contributors
6
+ License: Apache-2.0
7
+ Project-URL: Homepage, https://adrails.dev
8
+ Project-URL: Source, https://github.com/antonioac1/adrails
9
+ Keywords: mcp,advertising,google-ads,agents,guardrails
10
+ Classifier: Programming Language :: Python :: 3
11
+ Classifier: Programming Language :: Python :: 3.11
12
+ Classifier: License :: OSI Approved :: Apache Software License
13
+ Classifier: Operating System :: OS Independent
14
+ Requires-Python: >=3.11
15
+ Description-Content-Type: text/markdown
16
+ License-File: LICENSE
17
+ License-File: NOTICE
18
+ Provides-Extra: google
19
+ Requires-Dist: google-auth>=2.0; extra == "google"
20
+ Dynamic: license-file
21
+
22
+ # AdRails (adrails.dev)
23
+
24
+ **Guardrails for AI agents running your ads: an open-source, self-hosted Google Ads MCP server.**
25
+
26
+ Website and docs: https://adrails.dev · MCP Registry: `dev.adrails/adrails` · plain-text summary for agents: https://adrails.dev/llms.txt
27
+
28
+ AdRails is a local MCP server for Google Ads. An agent may read campaigns, status and search
29
+ terms as often as it likes; every write has to land in a reviewed desired-state file on disk,
30
+ get diffed against live state, and clear caps that live in a policy file no AdRails tool writes.
31
+ The Python package and module are still named `adsops` — that is the name you install and run.
32
+
33
+ Three things it does differently:
34
+
35
+ - **Your keys.** It runs on your machine against your own Google Cloud project and Google Ads
36
+ credentials. Nothing is hosted: the only endpoint the package talks to is the Google Ads API,
37
+ and credentials are read from the sources you configure (a service-account JSON file, a static
38
+ token, or a secret-manager lookup).
39
+ - **Your caps.** Caps live in a policy file that no AdRails tool writes; with `require_plan_id`
40
+ on, every commit must quote a fresh, single-use `plan_id` issued for that exact plan; and a
41
+ change that adds spend exposure is refused while the scheduled guard's heartbeat is stale.
42
+ - **Pay per call in sats.** Optional hosted add-ons, Lightning-first, metered per call in sats —
43
+ coming soon. Nothing in this release contacts any hosted service.
44
+
45
+ ## Testing
46
+
47
+ ```bash
48
+ python3 -m adsops --selftest # 430 unit checks, everything mocked
49
+ python3 tests/qa_invariants.py # 200 random sequences against a simulated Google Ads account
50
+ python3 tests/qa_inputs.py # hostile policy/state/config inputs (NaN, Infinity, bad dates, bad UTF-8, ...)
51
+ python3 tests/qa_secrets.py # canary tokens injected everywhere; none may reach output or logs
52
+ ```
53
+ The QA suites were written adversarially by a separate agent with no write access to `adsops/`, and every finding was fixed
54
+ or documented as intended behaviour.
55
+
56
+ ## What AdRails cannot guarantee
57
+
58
+ Read this before pointing it at a live account.
59
+
60
+ - **It is a threshold with automatic pause attempts, not a hard spend ceiling.** The guard
61
+ compares spend with numbers you wrote and issues pause operations. That is containment, not
62
+ billing control.
63
+ - **Google can deliver up to 2x the average daily budget on a given day.** A daily budget is an
64
+ average, not a maximum, and a pause is an API call that can be rejected or land late.
65
+ - **Reporting is delayed.** The spend figures AdRails reads are minutes to hours behind delivery.
66
+ - **The guard only acts when it is scheduled and the machine is awake.** A chat-session MCP
67
+ process is not a monitor: while the machine sleeps no checks run, spend keeps moving, and the
68
+ heartbeat goes stale.
69
+ - **An agent with shell access as the same user can bypass any local tool.** AdRails constrains
70
+ the tool calls it serves, not the machine underneath. Sandbox the agent if that matters to you.
71
+ - **Wrong negative keywords can suppress good traffic.** Negatives are append-only here, so a
72
+ bad one is also awkward to withdraw.
73
+ - **You are responsible for your account and your spend.** Keep platform-side billing limits as
74
+ the real ceiling.
75
+
76
+ ## Quickstart
77
+
78
+ **1. Install.**
79
+
80
+ ```bash
81
+ # from GitHub (PyPI release coming soon)
82
+ pipx install git+https://github.com/antonioac1/adrails # console script: adsops-mcp
83
+ # or run without installing:
84
+ uvx --from git+https://github.com/antonioac1/adrails adsops-mcp --config /absolute/path/config.json
85
+ ```
86
+
87
+ No other dependencies. Service-account tokens are signed with your system `openssl`
88
+ when `google-auth` isn't installed (install `google-auth` if you prefer it).
89
+
90
+ The core is stdlib-only. Check it offline (everything mocked, no network):
91
+
92
+ ```bash
93
+ python3 -m adsops --selftest # or: deploy/smoke_docker.sh
94
+ ```
95
+
96
+ **2. Write a config.** Every account, credential source and path lives here; paths are
97
+ `~`-expanded at load time.
98
+
99
+ ```json
100
+ {
101
+ "tenant": "your-tenant",
102
+ "meter_log": "~/.adsops/meter.jsonl",
103
+ "audit_log": "~/.adsops/audit.jsonl",
104
+ "plan_ledger": "~/.adsops/plans.jsonl",
105
+ "lock_dir": "~/.adsops/locks",
106
+ "guard_heartbeat": "~/.adsops/guard.heartbeat",
107
+ "credentials": {"google_ads": {"type": "service_account",
108
+ "sources": [{"kind": "file", "path": "~/.adsops/sa.json"}]}},
109
+ "google_ads": {"api_version": "v24", "end_field": "end_date_time", "login_customer_id": null},
110
+ "commit_policy": {"require_clean_git": true, "allow_commit": true, "allow_set": true},
111
+ "accounts": [{"key": "main", "platform": "google_ads", "customer_id": "000-000-0000",
112
+ "campaigns": [{"key": "search_core", "state_file": "~/ads/search_core.json",
113
+ "policy_file": "~/ads/search_core.policy.json"}]}]
114
+ }
115
+ ```
116
+
117
+ `commit_policy` defaults to `require_clean_git: true` and `allow_commit: false`, so commits and
118
+ `adsops_set` stay off until you turn them on.
119
+
120
+ **3. Write the policy file** for the campaign (next section), and commit both files to git so
121
+ `git diff` is the change review.
122
+
123
+ **4. Register the server** in your MCP client. Diagnostics go to stderr; the server speaks
124
+ JSON-RPC 2.0 over stdio, one object per line.
125
+
126
+ ```json
127
+ {
128
+ "mcpServers": {
129
+ "adrails": {
130
+ "command": "python3",
131
+ "args": ["-m", "adsops", "--config", "/absolute/path/config.json"]
132
+ }
133
+ }
134
+ }
135
+ ```
136
+
137
+ **5. Schedule the guard.** A chat session cannot watch spend, so the pause-only spend check runs
138
+ from your OS scheduler every 15 minutes. Templates for launchd, systemd and cron live in
139
+ `deploy/`; render the placeholders (`__PYTHON__`, `__CONFIG__`, `__PKG__`, `__LOGDIR__`) and read
140
+ `deploy/GUARD.md` before installing:
141
+
142
+ ```bash
143
+ PY=$(command -v python3); CFG=/absolute/path/config.json
144
+ PKG=/absolute/dir/containing/adsops; LOGDIR="$HOME/.adsops/logs"
145
+ mkdir -p "$LOGDIR"
146
+ sed -e "s|__PYTHON__|$PY|g" -e "s|__CONFIG__|$CFG|g" \
147
+ -e "s|__PKG__|$PKG|g" -e "s|__LOGDIR__|$LOGDIR|g" \
148
+ deploy/launchd/com.adsops.guard.plist.template \
149
+ > ~/Library/LaunchAgents/com.adsops.guard.plist
150
+ plutil -lint ~/Library/LaunchAgents/com.adsops.guard.plist
151
+ launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.adsops.guard.plist
152
+ ```
153
+
154
+ The command all three units run is `PYTHONPATH=$PKG $PY -m adsops --config $CFG guard-all`.
155
+
156
+ ## Use it from Grok, Claude Code, Cursor or any MCP client
157
+
158
+ AdRails is a local stdio server, so every client registers the same command. There is no hosted URL, by design.
159
+
160
+ ```bash
161
+ pip install git+https://github.com/antonioac1/adrails@v0.2.2
162
+
163
+ # Claude Code
164
+ claude mcp add adrails -- python3 -m adsops --config /absolute/path/config.json
165
+ # Grok CLI (it also reads ~/.claude.json, .cursor/mcp.json and .mcp.json)
166
+ grok mcp add adrails -- python3 -m adsops --config /absolute/path/config.json
167
+ ```
168
+
169
+ Cursor or a project `.mcp.json`:
170
+
171
+ ```json
172
+ {"mcpServers":{"adrails":{"command":"python3","args":["-m","adsops","--config","/absolute/path/config.json"]}}}
173
+ ```
174
+
175
+ Claude Desktop: install the `.mcpb` bundle from the [latest release](https://github.com/antonioac1/adrails/releases/latest).
176
+ More: https://adrails.dev/docs/mcp-clients/
177
+
178
+ ## Tools
179
+
180
+ | Tool | What it does |
181
+ | --- | --- |
182
+ | `adsops_campaigns` | Lists the campaigns this deployment may operate: keys, accounts, state files, and the active commit policy. |
183
+ | `adsops_status` | Live read for one campaign: status, end date, daily budget, spend today and lifetime, negative count, whether caps come from the policy file, and the guard heartbeat's age. |
184
+ | `adsops_terms` | Clicked search terms for the last N days (1–90, default 14): term, matched keyword, clicks, cost. |
185
+ | `adsops_plan` | Pure diff of the desired-state file against live state; writes nothing. Returns the operations, notes, `ops_count`, the exposure increases it found, and a single-use **`plan_id`** with its expiry. |
186
+ | `adsops_apply` | Validate-only unless `commit=true`. A commit needs `commit_policy.allow_commit`, a clean git-tracked state file, a fresh guard heartbeat when the change adds exposure, and the **`plan_id`** from `adsops_plan` when the policy requires it. |
187
+ | `adsops_set` | Proposes a budget / status / end-date / negatives change with a short `reason`; checks it against policy caps and live state, writes the state file and commits it to git. `dry_run=true` returns a **`plan_id`** instead of writing; `apply=true` needs that `plan_id` when the policy requires it. |
188
+ | `adsops_guard` | Reads spend and pauses the campaign if the daily or lifetime threshold is crossed. Pause only: it never enables, raises a budget or edits keywords. Validate-only unless `commit=true`. |
189
+ | `adsops_usage` | Metering summary for the tenant: calls, errors, units, ops and median latency per tool. |
190
+
191
+ ## The policy file
192
+
193
+ One policy file per campaign, referenced by `policy_file` in the config. AdRails only ever reads
194
+ it: no tool writes caps, and `adsops_set` refuses `guards` and `allow_enable` outright. If the
195
+ state file also carries caps they are ignored — the policy file always wins, and `adsops_status`
196
+ says so.
197
+
198
+ ```json
199
+ {
200
+ "customer_id": "000-000-0000",
201
+ "campaign_id": 1000000000,
202
+ "guards": {
203
+ "max_daily_budget_usd": 40,
204
+ "min_daily_budget_usd": 5,
205
+ "max_end_date": "2026-12-31",
206
+ "lifetime_spend_pause_usd": 900,
207
+ "daily_spend_pause_usd": 60,
208
+ "max_ops_per_run": 12
209
+ },
210
+ "allow_enable": false,
211
+ "max_guard_age_min": 30,
212
+ "require_plan_id": true,
213
+ "plan_ttl_s": 900
214
+ }
215
+ ```
216
+
217
+ | Field | Meaning |
218
+ | --- | --- |
219
+ | `customer_id` | Account the campaign lives in; compared with the state file after stripping dashes. A mismatch is refused. |
220
+ | `campaign_id` | The one campaign this policy governs; must match the state file exactly. |
221
+ | `guards.max_daily_budget_usd` | Required. Upper bound of the daily budget, and the budget ceiling checked at plan time. |
222
+ | `guards.min_daily_budget_usd` | Optional. Lower bound of the daily budget; must not exceed the maximum. |
223
+ | `guards.max_end_date` | Required, `YYYY-MM-DD`. Latest end date any plan may set. |
224
+ | `guards.lifetime_spend_pause_usd` | Required. Lifetime spend at which the guard issues a pause. |
225
+ | `guards.daily_spend_pause_usd` | Required. Today's spend at which the guard issues a pause. |
226
+ | `guards.max_ops_per_run` | Required integer. Most operations one run may emit; more is refused. |
227
+ | `allow_enable` | Default `false`. Whether a plan may ever set the campaign to `ENABLED`. |
228
+ | `max_guard_age_min` | Default `null` (check off). When set, any change that adds spend exposure is refused unless the guard heartbeat is younger than this. |
229
+ | `require_plan_id` | Default `false`. When `true`, apply/commit and `adsops_set` with `apply=true` must quote a `plan_id`. |
230
+ | `plan_ttl_s` | Default `900`, range 60–86400. How long an issued `plan_id` stays usable; each one is consumed once. |
231
+
232
+ A missing or malformed field is an error that names the field, not a silent default.
233
+
234
+ ## Desired-state file
235
+
236
+ One JSON file per campaign, referenced by `state_file`. It says what the campaign should look
237
+ like; the server computes the diff.
238
+
239
+ ```json
240
+ {
241
+ "customer_id": "000-000-0000",
242
+ "campaign_id": 1000000000,
243
+ "campaign_name": "Search - Core",
244
+ "status": "PAUSED",
245
+ "end_date": "2026-11-30",
246
+ "daily_budget_usd": 20,
247
+ "negatives_add": [
248
+ {"text": "free", "match_type": "BROAD"},
249
+ {"text": "cheap", "match_type": "PHRASE"}
250
+ ],
251
+ "guards": {
252
+ "max_end_date": "2026-12-31",
253
+ "min_daily_budget_usd": 5,
254
+ "max_daily_budget_usd": 40,
255
+ "lifetime_spend_pause_usd": 900,
256
+ "daily_spend_pause_usd": 60,
257
+ "max_ops_per_run": 12
258
+ }
259
+ }
260
+ ```
261
+
262
+ | Field | Meaning |
263
+ | --- | --- |
264
+ | `customer_id` | Account the campaign lives in; dashes are stripped before use. |
265
+ | `campaign_id` / `campaign_name` | The one campaign this file owns. Both must match live state or the run aborts. |
266
+ | `status` | Desired status, `ENABLED` or `PAUSED`. `ENABLED` additionally requires `allow_enable` in the policy. |
267
+ | `end_date` | Desired end date, `YYYY-MM-DD`, bounded by `guards.max_end_date` and not in the past. |
268
+ | `daily_budget_usd` | Desired daily budget, bounded by the min/max guard band. |
269
+ | `negatives_add` | Append-only list of `{text, match_type}`; match type is `BROAD`, `PHRASE` or `EXACT`. Nothing here removes a keyword. |
270
+ | `guards` | Read only when the campaign has no `policy_file` (legacy mode). With a policy file configured, these are ignored. |
271
+
272
+ Keep these files in git. That is what makes "reviewed desired state" real: `git diff` is the
273
+ change review, and `require_clean_git` makes the server refuse to act on uncommitted edits.
274
+
275
+ ## Works with Google's official read-only `google-ads-mcp`
276
+
277
+ Run both servers side by side in the same MCP client. Google's server answers ad-hoc GAQL
278
+ exploration and never writes; AdRails is the only write path. The agent reads with the official
279
+ server, proposes a change to a desired-state or policy file, and applies it through
280
+ `adsops_plan` / `adsops_apply` — with caps, a validate pass, an account lock, and an audit line
281
+ in between. Both speak JSON-RPC over stdio, so one `.mcp.json` entry each is the whole setup.
282
+
283
+ ## License
284
+
285
+ Apache-2.0.