Skip to main content
Glama

Honeyfield Marketing MCP

OpenAI Ads (Beta): List ads

openai_ads_list_ads
Read-only

BETA — Anzeigen einer Anzeigengruppe: id, name, status, review_status (OpenAI prüft jede Anzeige vor der Auslieferung) und creative (type z. B. chat_card, title, body, target_url, file_id). ad_group_id: aus openai_ads_list_ad_groups. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ad_group_id": "<ad_group_id>"
    },
    "name": "openai_ads_list_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo
ad_group_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only safety profile is covered. The description adds genuinely useful context beyond that — that OpenAI reviews every ad before delivery, which explains what review_status means — but says nothing about result limits, pagination, or ordering.

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 blocks with zero filler: the returned shape first, then the required parameter's provenance, then the optional parameter's default. Front-loaded and scannable.

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?

For a two-parameter read tool with an output schema, the essentials are present, but the field enumeration of the return shape duplicates what the output schema already declares and could have been spent on pagination or result-size behavior instead. Adequate, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameters, and it does: ad_group_id is tied to its source tool, and workspace is explained as a customer slug that may be omitted with a single workspace. Both of the two parameters get meaning beyond their bare types, though no ID format or slug example is given.

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 ('Anzeigen einer Anzeigengruppe' = list the ads belonging to one ad group) and enumerates the returned fields (id, name, status, review_status, creative). It implicitly distinguishes itself from openai_ads_list_ad_groups by naming that sibling as the source of the required ID, though it never explicitly contrasts with creatives/insights tools.

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?

Provides real prerequisites: ad_group_id must come from openai_ads_list_ad_groups, and workspace is optional when only one workspace exists. It does not state when to prefer this over alternatives such as openai_ads_insights or openai_ads_create_ad, so usage is implied rather than explicitly scoped.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources