> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superlaunch.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP workflows

> Use discovery, validation, writes, and result checks in the right order.

Start a workflow by discovering accessible objects and capabilities. Resolve required IDs, review the proposed change, submit it, then inspect the result.

## Rank campaign performance

1. Call `ad_accounts_list`.
2. Choose the accounts, dates, conversion event, and attribution window.
3. Use `insights_rank` for compact highest and lowest rankings.
4. Read the data-through date and warnings.

Set a minimum spend or conversion count to exclude results with too little data. For cost metrics such as CPA, lower values can be better.

## Create a draft rule

Call `rules_schema`, resolve accounts, and build the full rule definition. Supply a target filter, tasks with conditions and actions, and a schedule with time zone. Save as a draft with `dry_run: true`.

Read the rule back and run its current version in dry-run mode. Review decisions before activation. See [Rules](/guides/rules).

## Prepare a Launcher batch

Call `launcher_discover`, choose an account, and inspect saved creatives and templates. [Upload or import media](/launcher/media) if you need new files.

Approve exact creative versions, resolve the selection, inspect an existing target where required, and preview the launch. Submit with one stable request key. Poll the launch and operation records, including partial failures.

## Create Meta objects directly

Call `actions_capabilities` to check whether live changes are enabled. Creation and duplication tools default to `dry_run: true`; creation starts campaigns, ad sets, and ads paused.

For media, call `media_uploads_create` to open the upload picker when your client supports it. `media_uploads_complete` uploads one to ten selected files and returns a result for each file. Check those results before using the media.

For a signed upload without the picker, provide file metadata to `media_uploads_create`. Upload the file bytes using the returned URL, method, and headers before the URL expires. A successful upload saves the file in the workspace library. Use `media_asset_id` with Launcher tools or `media_id` with `creatives_create`.

Create a campaign, then an ad set, then an ad with the required parent IDs. Review dry-run results. Use a new request ID when changing the request from validation to live execution. Inspect the action result after execution.

## Reuse a successful setup

Use `campaigns_duplicate`, `adsets_duplicate`, or `ads_duplicate` to copy an existing Meta setup. Copies stay in the same account: an ad-set copy stays in its campaign, and an ad copy stays in its ad set. The copies start paused.

To use a setup in a different account, prepare a new launch with that account's assets and compatible template settings. Check its currency, Pages, pixels, audiences, and permissions before submitting.

For successful Launcher tests, choose **Promote successful tests** and select the source ads. See [Prepare and submit a launch](/launcher/launch).

## Save a confirmed fact

Resolve the scope, then call `memory_remember` only after an explicit save request or focused approval. Report the returned persistence state. Use `memory_recall` for relevant context and `memory_get` for an exact record.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.