Skip to main content
Glama

Metadata MCP Connector

Duplicate Campaign

duplicate_campaign

Duplicate (copy) an existing campaign into a NEW DRAFT campaign.

            KEYWORDS: duplicate, copy, clone, replicate, reuse, campaign, draft, copy of

            WHAT IT DOES:
            Creates a brand-new campaign that is a DEEP COPY of an existing one. The new
            campaign is created in DRAFT status and spends no budget. This mirrors the
            platform UI's "Duplicate campaign" action.

            WHAT GETS COPIED (server-side, automatic — there are NO toggles to choose):
            - Goal (Lead Gen / Brand Awareness)
            - Optimization (budget) group / tag
            - All landing pages
            - Every channel that is currently ENABLED FOR THE ACCOUNT, together with that
              channel's audiences, ads/creatives, keywords, offers and bid settings.
              (Channels that are disabled for the account are skipped — connect/enable the
              channel on the account first if you need it carried over.)

            WHAT IS NOT COPIED / CHANGES:
            - The new campaign starts in DRAFT (the original's live/active state is NOT copied).
            - Start/end dates are not carried as a live schedule — set them on the new draft.
            - Only the new name is caller-controlled.

            REQUIRED PARAMETERS:
            - campaign_id (integer): The wizard/campaign ID of the campaign to duplicate.
              Must be in status Launched, Launching, Editing, or Draft.

            OPTIONAL PARAMETERS:
            - name (string): The name for the NEW campaign. Must be non-blank, <= 255 chars,
              and UNIQUE across the account's campaigns. If omitted, a unique name is
              auto-generated as "<original name>_copy_<UTC timestamp>" (e.g.
              "Q1_2026_Campaign_copy_20260115120000"). If you pass a name that
              already exists on the account, the platform rejects it — choose a unique name
              or omit it to auto-generate one.

            CAMPAIGN ID SOURCES:
            - search_campaigns_by_names tool (recommended)
            - list_wizard_campaigns tool
            - get_campaign_by_wizard_id tool

            WORKFLOW:
            1. Find the source campaign ID (search_campaigns_by_names / list_wizard_campaigns).
            2. duplicate_campaign(campaign_id=..., name="..."  # name optional).
            3. The response contains the NEW campaign's id and full configuration.
            4. Review the new DRAFT campaign and MODIFY it with the edit tools below (it is a
               normal editable draft — change anything you want).

            AFTER DUPLICATING — HOW TO MODIFY THE NEW DRAFT:
            The copy is a regular DRAFT campaign, so use the standard campaign-editing tools on
            the NEW campaign id (NOT the original). The main ones:
            - add_and_edit_campaign_elements — the primary editor: rename, change budget group,
              start/end dates, enable channels, replace per-channel offers, and ADD audiences,
              exclusion audiences, ads, ad groups, and keywords. (Native / N×N×N campaigns:
              use add_and_edit_native_campaign_elements.)
            - update_experiments_daily_budgets — adjust per-experiment daily budgets.
            - update_reddit_channel_settings — Reddit-specific channel/bid/pixel settings.
            - remove_channels_from_campaign / remove_audiences_from_campaign /
              remove_ad_from_campaign / remove_keywords_from_campaign /
              remove_offers_from_campaign / remove_target_groups_from_campaign
              — remove elements from the copy.
            - manage_campaign — pause/restart (lifecycle).
            Tip: call get_campaign_by_wizard_id on the new id first to see what was copied,
            then edit. Use search_campaigns_by_names to re-locate the copy by its new name.

            EXAMPLE:
            User: "Make a copy of campaign 54050 called 'Q2 Relaunch'"
            Call: duplicate_campaign(campaign_id=54050, name="Q2 Relaunch")
            Then: add_and_edit_campaign_elements(campaign_id=<new id>, ...) to tweak the copy.

            RESPONSE FORMAT:
            Returns the full configuration of the newly created DRAFT campaign — including its
            new campaign id, name, status (Draft), goal, optimization group, and copied channels.
            Use the returned id with get_campaign_by_wizard_id and the edit tools.

            Anchor any date-derived naming to the REAL current date — call get_current_date if unsure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName for the new (copied) campaign. Must be unique on the account and <= 255 chars. Omit to auto-generate '<original name>_copy_<timestamp>'.
campaign_idYesThe wizard/campaign ID of the campaign to duplicate. Must be in status Launched, Launching, Editing, or Draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses key behaviors beyond the annotations: the new campaign is created in DRAFT status and spends no budget, the copy is a deep copy with certain elements included and others excluded (e.g., disabled channels are skipped), and there are NO toggles to choose. It also specifies that only the name is caller-controlled. This is rich, honest behavior disclosure that doesn't contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but exceptionally well-structured with clear headers, numbered workflow steps, and a concrete example. Some minor redundancy exists (the 'KEYWORDS' section and the second sentence repeating the first), but the overall organization makes it easy for an agent to consume. It uses headers and lists to break down a complex behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all necessary operational context: what is copied, what is not, parameter constraints and defaults, ID sourcing, step-by-step workflow, post-copy modification via sibling tools, an example call, and response format. It even advises calling get_current_date for name naming. Despite a complex tool with many downstream interactions, the description is fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds substantial semantic value. For campaign_id, it clarifies the acceptable statuses (Launched, Launching, Editing, or Draft). For name, it explains uniqueness requirements, auto-generation format with an example, and behavior when a duplicate name is provided. These details go beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear verb+resource+outcome: 'Duplicate (copy) an existing campaign into a NEW DRAFT campaign.' It further distinguishes the tool from siblings by noting it mirrors the platform UI's 'Duplicate campaign' actionaving also explains what is copied (deep copy) and what changes (status becomes draft). An agent can unambiguously identify when to use this tool and what it does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: a 'CAMPAIGN ID SOURCES' section recommends sibling tools (search_campaigns_by_names, list_wizard_campaigns) for finding the ID, a step-by-step WORKFLOW shows when to call duplicate_campaign, and an 'AFTER DUPLICATING' section clarifies that the resulting draft should be edited using specific sibling tools. It also states what is not copied and that the campaign ID must be in a certain status.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources