Skip to main content
Glama

Copy ad group to another platform

copy_ad_group

Copy an ad group to another platform its campaign runs on. The original is untouched; the copy has the same name, starts PAUSED, has no platform links and records copiedFrom. Ads of the same kind copy as they are (meta.overLimit lists text over the target's limits); ads of a different kind are rewritten as the target's format (meta.outcome rewrite); keywords on a platform without keywords become audienceSuggestion — a suggestion, not targeting. Returns the new ad group. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ad_group_id": "<ad_group_id>",
      "platform": "<platform>"
    },
    "name": "copy_ad_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesA platform the campaign runs on, other than the ad group's own.
space_idNoOverride the active Space for this one call. Defaults to the active Space set via set_active_space (or GROWOMAT_SPACE_ID on the server). Pass to read/write a different Space without changing the session binding.
ad_group_idYesThe ad group to copy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare that this is a non-destructive mutation; the description adds substantial context beyond that: the source is untouched, the copy starts PAUSED, has no platform links, and records copiedFrom. It also discloses edge-case behavior for same-kind ads (meta.overLimit), cross-kind ads (rewritten, meta.outcome rewrite), and keyword-to-audienceSuggestion conversion, which is exactly the kind of non-obvious behavior an agent needs before calling.

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?

Front-loaded with the core action and result, and every sentence carries information about behavior or scoping. It is dense and runs several clauses together (the ads/keywords sentence is long), so light structuring would improve scanability, but there is no filler.

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?

For a three-parameter mutation with no output schema, the description covers what is returned ('the new ad group'), the state of the copy, the fate of ads and keywords, and Space scoping. Nothing material needed to invoke it correctly is missing.

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 all three parameters are already documented, including the space_id override semantics. The description reinforces the platform constraint but adds no new format or syntax detail for the parameters themselves; its value is in explaining the copy outcome rather than parameter meaning.

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?

States a specific verb (copy) and resource (ad group) plus the destination constraint (another platform the campaign runs on). It is clearly distinguishable from create_ad_group or update_ad_group, since the description emphasizes that the original is untouched and a new ad group is produced.

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?

Usage is well framed: the target must be a platform the campaign already runs on and must differ from the ad group's own platform, which effectively defines when this tool applies. It also explains the Space scoping choice between set_active_space and the per-call space_id override. It stops short of explicitly contrasting copy vs. create_ad_group for a fresh ad group, so not a 5.

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