unarchive_campaigns
Put archived campaigns back, with a result per campaign.
Writes campaigns
Creates or changes something in the account. Put it behind whatever review your agent uses.
What it does
Put archived campaigns back, with a result per campaign.
An unarchived campaign is visible again under its name and no
experiment restarts. The exception is a campaign that was waiting
for its audiences to launch when it was archived: unarchiving
resumes that launch and it starts spending, so such a campaign
is only unarchived once its id is in confirm_pending_launch_ids.
KEYWORDS: unarchive, restore, undo archive, recover, put back, campaign
WHEN TO USE:
- The user asks to restore or unarchive campaigns, or to undo an
archive
- To find archived campaigns, call list_wizard_campaigns with
visibility ARCHIVED
Each campaign is processed on its own, so one that cannot be put
back does not stop the others. `results` holds one entry per
campaign with its `outcome`:
- unarchived
- not_archived: it is not archived; nothing changed
- not_in_account: no campaign with that id in this account
- native_imported: imported from an ad channel account, which is
never unarchived here
- pending_launch: unarchiving would resume its pending launch;
ask the user, then call again with only the campaigns the user
agreed to in confirm_pending_launch_ids
- name_taken: another visible campaign now holds its name, and
`holder` names it. Offer to rename the holder; once the user
agrees and it is renamed, unarchive again. Without a `holder`,
the archived campaign may hold the name itself. Never rename an
archived campaign: its name is what unarchive restores, so
renaming it blocks its own unarchive.
- not_attempted: the call stopped early (a rejected session or
rate limiting) before reaching it
- unknown: the platform's answer was lost; check the campaign
before trying again
- error: the platform refused it; `message` says why
PARAMETERS:
- campaign_ids (required): 1 to 50 campaign ids
- confirm_pending_launch_ids (optional): the campaigns, among
campaign_ids, whose pending launch the user agreed to resumeArguments
| Argument | Type | Notes | |
|---|---|---|---|
campaign_ids |
array | required | The ids of the campaigns to unarchive (1 to 50) |
confirm_pending_launch_ids |
array | Campaigns, among campaign_ids, whose pending launch (and spend) the user agreed to resume |
Request
Request template, not a complete runnable example. Replace placeholders, empty objects, arrays, and zero values with valid account-specific inputs. Read required fields and nested constraints in the full schema. Confirm the account, connected channels, and referenced assets before calling a write tool.
curl
curl -s -X POST https://mcp-server.metadata.io/mcp \
-H "Authorization: $METADATA_PAT" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "MCP-Protocol-Version: 2025-11-25" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"unarchive_campaigns","arguments":{"campaign_ids":[]}}}'Response
No recorded response. This tool writes to the account, so it is never executed to build these docs.
The request is an illustrative template. Fill required fields and check the current schema before calling it. No response is fabricated.
Related
Other campaigns tools: