openai-ads-mcp

pause_ads

Pause multiple ads at once with reversible action. Reports failures per ad ID without interrupting the batch.

Instructions

Pause many ads at once (reversible). Failures are reported per id, not fatal.

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_ids": "<ad_ids>"
    },
    "name": "pause_ads"
  }
}

Input Schema

Name	Required	Description	Default
`ad_ids`	Yes

Output Schema

Name	Required	Description	Default
`action`	Yes
`succeeded`	No
`failed`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 17, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Description adds value beyond annotations by stating the operation is reversible and that failures are per-id and non-fatal. Annotations already indicate not read-only and not destructive, but the description clarifies that it is a mutation that is not destructive (reversible). No contradiction.

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?

Extremely concise: one sentence conveying core functionality and key behavioral traits. No unnecessary words, well front-loaded.

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?

With an output schema present, return values are covered externally. The description covers batch pausing, reversibility, and error handling. Missing details on prerequisites, rate limits, or impact on related entities, but sufficient for basic understanding of a batch operation.

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 coverage is 0%, so description must compensate. Only the parameter name 'ad_ids' is implicit from the operation. The description does not explain format, constraints, or how identifiers are used, providing minimal added semantic value.

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?

The description clearly states the verb 'pause', resource 'ads', and specifies 'many at once' as a batch operation. It also mentions reversibility and error handling, distinguishing it from siblings like 'archive_ads' which may be irreversible.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. Sibling tools include 'archive_ads' and 'set_status', but the description does not help select between them.

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

Deploy Server