Skip to main content
POST
Enable a Google Ads ad.
Change — approval required. Calling this tool does not change your ad account. ADSMCP checks the arguments and stages the change as a pending action. It runs only after a person approves it on the dashboard Approvals page. Over MCP or REST you can view (list_pending_actions) or reject (manage_action) it, never approve it. execution_mode and similar arguments do not skip the queue.Spend cap. When the approved change runs, ADSMCP adds up the daily budgets of everything that would be spending in the platform’s connected accounts after the change. If that total is above your Max Daily Budget (dashboard Brand page), the change is refused. If the total cannot be read, it is refused too.A change that fails when it runs is not retried automatically. It shows on the dashboard Execution Queue.
Enable a Google Ads ad. Platform: Google Ads · Type: Change

How to call it

  • MCP: on https://mcp.adsmcp.si/mcp, run it through the google_ads_write tool with {"action": "execute", "tool_name": "enable_google_ad", "arguments": { ... }}, or call enable_google_ad by name. search_tools finds it and get_tool_schema returns its arguments; https://mcp.adsmcp.si/mcp/flat lists every tool by name.
  • REST: POST https://mcp.adsmcp.si/api/v1/tools/enable_google_ad/execute with Authorization: Bearer sk_live_... and a JSON body {"platform": "google", "arguments": { ... }}. The arguments are listed below; they are exactly the tool’s input schema.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Authorization
string
required

Bearer token

Idempotency-Key
string

Body

application/json
platform
string
default:google
arguments
object

Response

Tool execution result.

ok
boolean
required
platform
string
required
tool
string
required
error
null | object
required
mcp_response
any
required
data
any