ChatGPT Ads MCP server

openai ads get feeds

openai_ads_get_feeds

Read-onlyIdempotent

Lists the product feeds for a ChatGPT Ads advertiser account, with optional product counts and paginated results, so you can review feed inventory before preparing ad changes.

Instructions

List the account's product feeds, optionally with product counts. 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.

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety behavior is covered. The description adds that native fields and pagination are preserved, which tells the agent to expect pass-through upstream shapes rather than normalized ones. It says nothing about rate limits, page sizes, or whether counts are expensive to compute.

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 core action, no filler. The final sentence is the weakest link and could be dropped or corrected without loss.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and parameter coverage is complete in the schema. What is missing is the piece an agent actually needs for selection: how this differs from get_feed_products/get_feed_uploads, and why a read tool would defer nested request detail to a write-schema tool.

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 baseline is 3. The description does hint at the 'include: product_count' option and the pagination parameters, but adds no syntax or constraints beyond what the schema already documents (limit 1-500, after/before cursors, adacct_ ID scoping).

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 the account's product feeds', with an optional enrichment (product counts). It is clearly a feeds listing, not uploads or settings, though it does not explicitly name the neighboring feed tools (get_feed_uploads, get_feed_settings, get_feed_products) to sharpen the boundary.

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

Usage Guidelines2/5

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

No guidance on when to use this vs get_feed_products or get_feed_uploads, both of which overlap semantically with 'feeds'. The only routing hint, 'See openai_ads_get_write_schema for nested request fields', points at a write-schema tool for what is a read-only list operation, which is more likely to confuse than help.

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

Deploy Server