Skip to main content
Glama
Sign In
OpenAI Ads MCP

OpenAI Ads MCP

by trakkr-aisearch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_ad_groups

Read-onlyIdempotent

Retrieve ad groups from your OpenAI Ads account, optionally filtered by campaign and with pagination controls.

Instructions

List ad groups, optionally filtered to a campaign.

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": "list_ad_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idNo
limitNo
afterNo
beforeNo
orderNodesc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds no behavioral context beyond the filter option mentioned in schema. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single short sentence, front-loaded with purpose. However, given the tool has 5 parameters including pagination, the description is underspecified and could benefit from more structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and description does not hint at what the response contains (e.g., list of ad group objects). Missing pagination context for after/before parameters, which are crucial for list operations.

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

Parameters2/5

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

Schema description coverage is 0%. Description only references 'campaign_id' implicitly. Does not explain pagination parameters (limit, after, before) or ordering (order). Fails to compensate for lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states verb (list), resource (ad groups), and condition (optionally filtered to a campaign). Distinguishes from sibling tools like list_ads or list_campaigns by specifying the resource type.

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?

Implied usage: use to list ad groups. No explicit guidance on when to use vs alternatives, no exclusions or prerequisites mentioned. Adequate but minimal.

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

Deploy Server

Other Tools