Skip to main content
Glama
kadam-official

@kadam-net/mcp-server

Official
by kadam-official
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

kadam_adv_copy_campaign

Copy an ad campaign's targeting, bids, limits, and creatives into a new paused campaign that goes through moderation, without copying statistics or spend.

Instructions

Copy a campaign. Targeting, limits and bids are cloned into a new campaign; statistics and spend are not. The copy always starts paused and goes through moderation again, so it does not spend until activated. Creatives are copied too (all of them by default) and are moderated as new ones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCampaign ID to copy
bidNoBid for the new pricing model (target CPA cost for cpa_target)
nameYesName for the new campaign
folderIdYesCampaign group the copy is created in
countriesNoComma-separated ISO country codes the new bid applies to (e.g. 'US,DE')
creativesNoWhich creatives to copy: all of them, or only the active ones. Default: all
targetTypeNoCopy into another ad format. Only push <-> inpage_push is supported, and the source campaign must be one of the two
copySiteBidsNoCopy per-site bids and multipliers in the background. Ignored without extended-stats access; rejected when the target group belongs to an account with another currency
pricingModelNoSwitch the copy to another pricing model. Requires bid + countries, because the new model prices geo differently and the source bids cannot be reused
copyAutorulesNoCopy the campaign's autorules. Ignored for accounts without autorules access and for non-CPC campaigns
pauseAfterModerationNoKeep the copied creatives paused once moderation passes. Default: true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, so the description carries real weight and delivers: what is cloned (targeting, limits, bids) vs not (stats, spend), that the copy starts paused, re-enters moderation, does not spend until activated, and that creatives are copied and re-moderated as new. This is exactly the behavioral context an agent needs for a mutation.

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?

Three tight sentences, front-loaded with the core action, and each one adds a distinct behavioral fact without redundancy. Zero filler.

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?

For a mutation tool with no output schema this is strong: the description explains post-copy state, moderation, and spend behavior comprehensively. It is slightly short of perfect because return/result expectations are unaddressed, though the schema covers all inputs.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 11 parameters with detailed semantics. The description adds no extra parameter syntax or format detail beyond what the schema provides (its 'all by default' note merely restates the creatives schema default), so the baseline 3 applies.

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

Purpose4/5

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

The opening verb+resource ("Copy a campaign") is specific and clearly distinct from create_campaign/update_campaign, and the following sentences sharpen the meaning by stating exactly what is cloned. It stops short of an explicit sibling comparison, so it misses the top tier.

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

Usage Guidelines3/5

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

Usage is implied: this duplicates an existing campaign rather than creating one from scratch, and the paused/moderation behavior is stated. However there is no explicit when-to-use, when-not, or alternative (e.g. create_campaign) guidance, so it stays at implied usage.

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

Deploy Server

Other Tools