Skip to main content
Glama

duplicate_campaign

Duplicate a campaign and its child ad sets and ads within the same account. All created objects are paused. Reuse creatives and optionally override ad set budgets.

Instructions

Duplicate a campaign (and optionally its child ad sets and ads) within the same account.

All created objects are PAUSED. When include_ads=True, ads are duplicated with their existing creative references (creatives are reused, not copied).

Same-account only. Cross-account duplication is not supported.

Args: campaign_id: Source campaign ID to duplicate. account_id: Ad account ID. Must match the source campaign's account. name_suffix: Appended to source names (default " - Copy"). Must result in valid names per naming convention. include_adsets: Whether to duplicate child ad sets (default True). adset_budget_override: Override all duplicated ad set budgets (EUR). Only applies to ABO campaigns. If None, copies source budgets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes
account_idYes
name_suffixNo - Copy
include_adsetsNo
include_adsNo
adset_budget_overrideNo
Behavior4/5

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

With no annotations provided, the description fully covers behavioral aspects: 'All created objects are PAUSED' and 'when include_ads=True, ads are duplicated with their existing creative references (creatives are reused, not copied).' Lacks details on idempotency or rate limits but overall strong.

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

Conciseness5/5

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

Well-structured: core purpose first, then constraints, then Args section. Every sentence is informative with no redundancy. Appropriate length for the tool's complexity.

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

Completeness4/5

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

Covers purpose, parameter semantics, and key behavioral notes despite no output schema or annotations. Could mention error handling or return format, but overall provides sufficient context for correct invocation.

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?

Schema coverage is 0%, so description must add meaning. It provides detailed explanations for all 6 parameters: purpose of campaign_id, account_id, name_suffix (with default and constraint), include_adsets, include_ads, and adset_budget_override (with ABO context and currency). Adds significant value beyond field names.

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?

Clearly states 'Duplicate a campaign (and optionally its child ad sets and ads) within the same account.' This specific verb-resource combination distinguishes it from sibling 'duplicate_adset' and includes scope constraint.

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

Usage Guidelines4/5

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

Explicitly states 'Same-account only. Cross-account duplication is not supported,' providing a clear when-not-to-use condition. Does not explicitly mention alternatives (e.g., duplicate_adset) but usage context is adequate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brandu-mos/konquest-meta-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server