Skip to main content
POST
Disabled from MCP and REST: queued actions run only after a person approves them in the dashboard. Always refused with approval_requires_dashboard; use list_execution_queue to view.
Always refused over MCP and REST with approval_requires_dashboard. Only a person can approve, run or retry a change, on the dashboard Approvals page. This tool exists so an AI client gets a clear answer instead of an unknown-tool error.
Disabled from MCP and REST: queued actions run only after a person approves them in the dashboard. Always refused with approval_requires_dashboard; use list_execution_queue to view. Platform: ADSMCP (registered under meta) · Type: Control

How to call it

  • MCP: on https://mcp.adsmcp.si/mcp, run it through the meta_ads_write tool with {"action": "execute", "tool_name": "execute_queued_action", "arguments": { ... }}, or call execute_queued_action 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/execute_queued_action/execute with Authorization: Bearer sk_live_... and a JSON body {"platform": "meta", "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:meta
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