Skip to main content
Glama

Honeyfield Marketing MCP

OpenAI Ads (Beta): Account

openai_ads_account
Read-only

BETA — OpenAI-Ads-Werbekonto (Anzeigen in ChatGPT): id, name, status, review_status (Marken-Prüfung; ohne approved liefert das Konto nicht aus), review_reason, currency, timezone, url. Guter erster Aufruf, um zu prüfen, ob der hinterlegte Schlüssel zum richtigen Konto gehört. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "openai_ads_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds context the annotations don't carry: review_status is a brand review gate and the account will not serve ads unless it is 'approved'. That is a meaningful behavioral fact an agent cannot infer from structured fields, though other traits (rate limits, beta restrictions, what the URL field represents) are not covered.

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?

It is a compact two-part block that front-loads the returned field set, then the usage hint, then the parameter note. The field enumeration is slightly redundant with the output schema, but each field carries semantic weight (especially review_status), so little is wasted.

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 restate return shapes, and it focuses instead on the delivery-gating review_status fact and the optional workspace scoping — the two things an agent needs to call and interpret this correctly. The remaining gap is minor: no note on beta limitations or failure modes when the key maps to the wrong account.

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 description coverage is 0%, so the description must compensate, and it does: it defines 'workspace' as the customer workspace slug and says it is optional when the key resolves to a single workspace. That explains both the meaning and the conditional optionality of the only parameter, though it does not state how the slug is obtained.

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?

The description states a concrete verb and resource: it fetches the OpenAI Ads account including id, name, status, review_status, review_reason, currency, timezone and url. This is clearly distinct from the openai_ads_create_* / list_campaigns siblings, which operate on campaigns, ads or conversion settings rather than on account-level metadata. It stops short of naming any sibling as the tool to use for those adjacent tasks.

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

Usage Guidelines4/5

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

'Guter erster Aufruf, um zu prüfen, ob der hinterlegte Schlüssel zum richtigen Konto gehört' gives a clear use context: a first/verification call to validate account credentials. There is no explicit when-not guidance and no alternative tool is named, so it lands just below the top band.

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