Change approval workflow
Loading server catalog…. Download catalog
Advarde MCPAvailable subject to your connection’s permissions.
Description: Prepare, inspect, approve, and apply the exact requested change.
Documentation: Getting started
Output: See the protocol description and workflow notes below.
Access: Workspace-scoped MCP authentication.
Prepare and review
Upstream write tools prepare a proposal rather than immediately changing Ads resources. Inspect its account, payload, before-state, budget, schedule, and intended state transition. Workspace-saving tools may write directly; check each tool’s behavior and description.
Apply after authorization
Call ads_apply_change with the reviewed change_id and confirmed: true only after the user authorizes that exact action. A Boolean is not independent evidence of human consent. Proposals normally expire after 15 minutes.
Creation and activation
Normal campaign creation starts paused. Launch is a separate reviewed action. Some actions activate spending or permanently archive resources. There is no automatic rollback; inspect results and preserve known successful work.
Authentication
Use an MCP access token from MCP connections, or connect through OAuth. Send your token in the Authorization: Bearer header.
For full protocol initialization and tool discovery, use an MCP client. These examples show individual JSON-RPC requests.
Responses
200Successful protocol response
Inspect result.isError for tool-level failures, even when the HTTP status is 200.
202Notification accepted
MCP notifications return no JSON-RPC response body.
400Invalid request
Check the JSON-RPC envelope, parameters, and protocol version.
406Not acceptable
Accept must include application/json and text/event-stream.
429Rate limited
Wait for the Retry-After interval before making another request.
401Unauthorized
A valid, unexpired MCP bearer token is required.
403Access denied
Your connection needs access to this workspace and the requested operation.