openai-ads-mcp

set_status

Destructive

Activate, pause, or archive campaigns, ad groups, or ads with a single lifecycle transition. Confirm required for irreversible archive.

Instructions

Apply a single lifecycle transition to a campaign, ad group, or ad.

Note: pausing a campaign or ad group does NOT change its children's status (they stay 'active' but stop serving). archive is IRREVERSIBLE and removes the object from all list views — it requires confirm=true (matching archive_ads); prefer action="pause" unless you are certain.

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": {
      "kind": "<kind>",
      "resource_id": "<resource_id>",
      "action": "<action>"
    },
    "name": "set_status"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes
`resource_id`	Yes
`action`	Yes
`confirm`	No

Output Schema

Name	Required	Description	Default
`kind`	Yes
`id`	Yes
`status`	No
`review_status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations indicate destructiveHint=true, but description adds critical detail: archive is IRREVERSIBLE and removes from list views, pausing does not change children's status. No contradiction with annotations.

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?

Four sentences, front-loaded with main purpose, each sentence adds distinct value. No unnecessary words or repetition.

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?

Has output schema so return values are covered. Description explains key behaviors for each action but does not cover error conditions or required permissions. Still reasonably complete for a lifecycle tool.

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?

Despite 0% schema coverage, description explains the effect of each action (pause vs archive) and required confirm for archive. Lacks details on activate behavior but adds significant meaning beyond enum values.

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 it applies a single lifecycle transition to campaign, ad group, or ad. It differentiates from sibling tools like archive_ads and pause_ads by mentioning archive requires confirm=true matching archive_ads and preferring pause unless certain.

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

Usage Guidelines5/5

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

Explicitly advises when to use pause vs archive ('prefer action="pause" unless you are certain'), warns about children not changing when pausing, and notes archive is irreversible. Provides clear alternatives and context.

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

Deploy Server