ChatGPT Ads MCP server

openai ads get ads

openai_ads_get_ads

Read-onlyIdempotent

Lists one page of ads in an ad group with native creative metadata and review status, plus optional serving issues. Use cursor paging to retrieve and review ad details.

Instructions

List one page of ads in an ad group with native creative metadata and review status. Follow last_id only when has_more is true.

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.
`adGroupId`	Yes	Native ad group ID (adgrp_) in the configured 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.

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

Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description adds real behavioral context: results arrive as a single page and cursors should only be followed when has_more is true. It stops short of stating anything about filtering behavior, the account-scoping constraint, or the effect of include=serving_issues, which the schema carries alone.

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?

Two short sentences, zero waste, and the primary operation is stated before the pagination caveat. Every clause carries information.

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, the description needn't explain return fields, and the pagination contract is stated. What's missing is a note on the account scoping constraint or how the include parameter changes the response, but those are already covered in the schema.

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 every one of the eight parameters is already documented, and the baseline of 3 applies. The description mentions cursor semantics but refers to 'last_id' (a response field) rather than the 'after' parameter name, so it adds little usable meaning beyond the schema and risks a naming mismatch.

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 ads in an ad group') plus the content returned (native creative metadata and review status). This clearly separates it from openai_ads_get_ad, which fetches a single ad, but it doesn't name that sibling or contrast the two explicitly.

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 clear guidance for paging, which is implied usage. But there is no statement of when to prefer this over openai_ads_get_ad or a creative-listing tool, and nothing about exclusions or prerequisites.

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

Deploy Server