ChatGPT Ads MCP server

openai ads get feed products

openai_ads_get_feed_products

Read-onlyIdempotent

Lists products in a feed that match ad group product filters, preserving native fields and pagination so you can retrieve exact ad-targeted catalog items.

Instructions

List products in a feed that match ad group product filters. Native fields and pagination are preserved. See openai_ads_get_write_schema for nested request fields.

Input Schema

Name	Required	Description
`body`	Yes	Exact pinned native JSON request body. Nested configuration objects replace their previous contents, so send the complete intended configuration. Money uses integer account-currency micros.
`feed_id`	Yes	Exact native feed_id. The entity must belong to the configured ad account.
`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 / body / properties / filters / items / properties / operator / anyOf

Added value: +[
+  {
+    "const": "in",
+    "type": "string"
+  },
+  {
+    "const": "not_in",
+    "type": "string"
+  },
+  {
+    "const": "gt",
+    "type": "string"
+  },
+  {
+    "const": "gte",
+    "type": "string"
+  },
+  {
+    "const": "lt",
+    "type": "string"
+  },
+  {
+    "const": "lte",
+    "type": "string"
+  },
+  {
+    "const": "contains",
+    "type": "string"
+  },
+  {
+    "const": "not_contains",
+    "type": "string"
+  },
+  {
+    "const": "starts_with",
+    "type": "string"
+  }
+]

removedInput schema / properties / body / properties / filters / items / properties / operator / enum

Removed value: -[
-  "in",
-  "not_in",
-  "gt",
-  "gte",
-  "lt",
-  "lte",
-  "contains",
-  "not_contains",
-  "starts_with"
-]

removedInput schema / properties / body / properties / filters / items / properties / operator / 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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds only that 'native fields and pagination are preserved' — a useful but thin note on response shaping, with no mention of the filter semantics (e.g., that product filters come from the ad group) or limits.

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 verb and resource, with no filler. The final cross-reference sentence is terse but arguably misdirects toward a write-schema tool, which slightly weakens an otherwise clean structure.

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, so return values need not be explained, and the fully-described schema covers all three parameters including the nested body. What remains missing — guidance on choosing this tool over the other feed-related siblings — is a usage gap rather than a completeness gap at the schema level.

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 explains adAccountId scoping, feed_id ownership, and the body's complete-configuration semantics including micros currency. The description adds nothing beyond pointing at another tool for 'nested request fields', so the 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 products in a feed') plus the scoping condition ('that match ad group product filters'), which distinguishes it from sibling listing tools like openai_ads_get_feeds or openai_ads_get_feed_settings. It does not explicitly name those siblings as alternatives, keeping it short of a 5.

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?

There is no statement of when to use this tool versus openai_ads_get_feeds, openai_ads_get_feed_uploads, or openai_ads_get_feed_settings, and no prerequisites or exclusions. The only routing hint ('See openai_ads_get_write_schema for nested request fields') points at a write-schema tool for what is described as a read/list operation, which is confusing rather than directive.

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

Deploy Server