ChatGPT Ads MCP server

openai ads get audit logs

openai_ads_get_audit_logs

Read-onlyIdempotent

Lists recorded campaign, ad group, and ad changes with filters for entity, actor, and time so you can audit account activity.

Instructions

List recorded changes to the account's campaigns, ad groups and ads, optionally filtered by entity, actor or time. Native fields and pagination are preserved. See openai_ads_get_write_schema for nested request fields.

Input Schema

Name	Required	Description	Default
`query`	No	Documented native query parameters. Each call reads one page unless the tool says otherwise.
`adAccountId`	Yes	The adacct_ ID configured in OPENAI_ADS_ACCOUNT_ID. The API key is scoped to this one account; another ID is refused.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026

addedInput schema / properties / query / properties / order / anyOf

Added value: +[
+  {
+    "const": "asc",
+    "type": "string"
+  },
+  {
+    "const": "desc",
+    "type": "string"
+  }
+]

removedInput schema / properties / query / properties / order / enum
```
Removed value: -[
-  "asc",
-  "desc"
-]
```
removedInput schema / properties / query / properties / order / type
```
Removed value: -"string"
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv1.0.0Oct 23, 2026

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds that native fields and pagination are preserved (one page per call), which is useful context, but says nothing about retention window or volume of results. The trailing reference to openai_ads_get_write_schema is confusing on a read-only log tool and adds no behavioral clarity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the resource and scope. The final sentence about write schema is the only weak link — it points at a mutation tool from a read tool and slightly dilutes focus.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, annotations are rich, and the parameter schema is fully documented, so the description only needs to establish scope and pagination — which it does. The odd write-schema redirect is the sole incompleteness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all eleven query fields are already documented, including the nested roll-up semantics for campaign_id and ad_group_id and the actor_id caveat. The description only restates the filter axes at a higher level, so it sits at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'List recorded changes to the account's campaigns, ad groups and ads' — which is unmistakably distinct from the get_campaigns/get_ads retrieval siblings. An agent can tell this is the audit-history tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the filter dimensions (entity, actor, time) which implies when to reach for it, but gives no explicit when-not or alternative routing. The pointer to openai_ads_get_write_schema is a cross-reference for related fields rather than a usage rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server