list_campaignsList ad campaigns in your OpenAI Ads account with cursor pagination, configurable limits, and creation-time sorting for efficient campaign management.
List campaigns in the current OpenAI Ads account with pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor for pagination | |
| limit | No | Number of items to return (1-500). Default 20. | |
| order | No | Sort order by creation time | |
| before | No | Cursor for previous page |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full behavioral burden. 'List' implies a read-only operation and 'with pagination' discloses how results are returned, but no output format, rate limits, or side-effect notes are provided. Adequate but minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no filler. It states the operation, scope, and pagination behavior efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list tool, the description plus a fully documented schema covers core invocation needs. The lack of an output schema means the return shape is not disclosed, and no sibling routing is provided, but these are minor gaps given the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with all four parameters (after, limit, order, before) already described. The description adds no parameter-specific meaning, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists campaigns in the current OpenAI Ads account and explicitly mentions pagination. This distinguishes it from sibling tools like get_campaign (singular retrieval) and create_campaign/update_campaign (mutations).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The use case is implied by the verb 'list' and the scope 'current account', but no explicit alternatives or exclusions are given. An agent must infer when to choose this over get_campaign or other campaign tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.