Skip to main content
Schedules use saved template and selection settings. Read the current version before editing. Existing runs keep their original settings. Account limits cap Launcher campaign counts and configured budgets; they do not cap all spending in Meta. The tables list arguments and common nested fields. Expand Full input schema for all fields and allowed values. Workspace and account permissions apply to every tool.

launcher_schedules_create

Create a recurring launch with saved template and selection settings. Overlapping runs are skipped. Access: mcp:read and mcp:write.

data fields

Retries: after a timeout, read the current state before submitting again to avoid duplicate changes.

launcher_schedules_change_status

Pause or resume future scheduled runs. Runs already created keep their saved settings. Access: mcp:read and mcp:write. Retries: read the current state after a timeout. If the change has already applied, do not submit it again with an old version.

launcher_schedules_list

List recurring launches for an account. Access: mcp:read.

launcher_schedules_get

Read a schedule definition and exact version references. Access: mcp:read.

launcher_schedules_update

Update settings for future runs. Runs already claimed for execution keep their original settings. Access: mcp:read and mcp:write.

data fields

Retries: after a timeout, read the current state before submitting again to avoid duplicate changes.

launcher_account_limits_get

Read the account’s Launcher campaign-count and configured-budget limits. Access: mcp:read.

launcher_account_limits_update

Set the account’s Launcher limits. Omit the expected version only when configuring limits for the first time. Access: mcp:read and mcp:write.

data fields

Retries: after a timeout, read the current state before submitting again to avoid duplicate changes.