Skip to main content
Glama

duplicate_adset

Duplicate a single ad set into a target campaign within the same account. The new ad set is created paused, without child ads.

Instructions

Duplicate a single ad set into a target campaign within the same account.

All created objects are PAUSED. Does not duplicate child ads. Same-account only.

Args: adset_id: Source ad set ID to duplicate. target_campaign_id: Campaign to place the duplicated ad set in. account_id: Ad account ID (must match source). name_suffix: Appended to source name (default " - Copy"). budget_override: Override budget in EUR. If None, copies source budget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adset_idYes
target_campaign_idYes
account_idYes
name_suffixNo - Copy
budget_overrideNo
Behavior4/5

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

Discloses key behaviors: created objects are paused, child ads are not duplicated, and budget override behavior. Lacks info on error handling or return value, but no annotations are present.

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?

Very concise with a clear summary followed by bullet-pointed args; every sentence adds value without redundancy.

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 input semantics and constraints well, but lacks description of the return value (e.g., ID of duplicated ad set) which would be helpful given no output schema.

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?

The description explains each parameter's purpose and defaults (e.g., budget_override in EUR, name_suffix default), significantly adding meaning beyond the input schema's bare property 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?

The description clearly states the tool duplicates a single ad set into a target campaign within the same account, distinguishing it from siblings like 'duplicate_campaign' and noting it does not duplicate child ads.

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 mentions same-account only and that created objects are paused, but does not compare to alternatives like 'create_adset' or specify when not to use it.

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