ChatGPT Ads MCP server

openai ads get campaigns

openai_ads_get_campaigns

Read-onlyIdempotent

Retrieve a paginated list of active campaigns within your ad account. Specify the required ad ID to manage and view your current advertising initiatives.

Instructions

List one page of campaigns in the account. Follow last_id only when has_more is true. Budget amounts use integer account-currency micros.

Input Schema

Name	Required	Description	Default
`name`	No	Return only entities whose name matches this text, 3 to 1,000 characters.
`after`	No	Next-page cursor: the previous page's last_id, only when has_more is true.
`limit`	No	Page size, 1 to 500. Defaults to 100.
`order`	No	Sort by creation time. Defaults to desc, newest first.	desc
`before`	No	Previous-page cursor: a first_id returned by a later page.
`include`	No	Add serving_issues to receive native reasons why this entity cannot serve. A paused state is intentional, not an issue.
`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.

Changed1 schema field changedOct 26, 2026

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.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real value by disclosing that results are paged one page at a time and that budget values are integer micros in account currency, which prevents a common misread of returned numbers.

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

Conciseness5/5

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

Three short sentences, front-loaded with the verb and scope, then pagination rule, then unit convention. Nothing is padded or repeated from the schema.

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?

With an output schema present, return values need not be explained, and the description covers pagination and unit conventions. It leaves unmentioned the filtering and sorting capabilities the schema exposes, but nothing required for a correct call is missing.

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 the schema already documents every input including the 'after' cursor, limit, order and include. The description reinforces the cursor contract by referring to last_id/has_more, but adds no new meaning for name, limit, order, before or include, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('List one page of campaigns in the account'), and 'one page' implicitly contrasts with the singular openai_ads_get_campaign sibling. It stops short of naming the sibling or noting that this returns summary-level campaign objects.

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?

The pagination rule ('Follow last_id only when has_more is true') gives operative guidance for continuation, but there is no explicit statement of when to reach for this list tool versus openai_ads_get_campaign or openai_ads_get_insights.

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

Deploy Server