Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_copy_campaign

Copies a Snapchat campaign with its ad squads and ads into a new paused campaign, scaling budgets and re-timing start, with a preview step before applying changes.

Instructions

Copy a campaign with its ad squads (and optionally ads) into a NEW campaign. Everything is created PAUSED and re-timed to start shortly after enabling. Daily and lifetime budgets are scaled by budget_scale and must stay within the configured limits. Previews unless confirm=true. Review in Ads Manager, then enable with snap_set_status. Two steps: confirm=false returns a preview and an approval_token; to apply, repeat the same arguments with confirm=true and that approval_token.

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": {
      "campaign_id": "<campaign_id>",
      "new_name": "<new_name>"
    },
    "name": "snap_copy_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
new_nameYes
squad_idsNoCopy only these ad squads of the source campaign
campaign_idYes
include_adsNo
budget_scaleNoMultiply every daily and lifetime budget, e.g. 0.5 for half
approval_tokenNoThe approval_token returned by the preview of this exact request. Required with confirm=true.
resume_campaign_idNoReuse an empty campaign left by a failed copy instead of creating a new one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the safety profile (not read-only, not destructive, not idempotent, open-world); the description goes well beyond that by disclosing that everything is created PAUSED and re-timed, that budgets are scaled and must stay within configured limits, and that a preview/approval_token handshake gates the apply step. That handshake also explains why idempotentHint=false, and creating new entities is consistent with destructiveHint=false.

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 purpose, then safety state, then the confirm flow — good ordering. Slight redundancy between 'Previews unless confirm=true' and the later 'confirm=false returns a preview', but no sentence is wasted.

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 an 8-parameter mutation tool with no output schema, the description covers the essentials: side effects (paused, re-timed), validation constraints (budget limits), and the approval workflow. It does not describe what the preview response contains beyond the approval_token or how partial failures interact with resume_campaign_id.

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

Parameters4/5

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

Schema coverage is 63% and the description fills the most important gap: the exact two-step protocol for confirm and approval_token ('repeat the same arguments with confirm=true and that approval_token'). It also clarifies that include_ads is optional and that budget_scale applies to every daily and lifetime budget, though resume_campaign_id and squad_ids are left to the schema.

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 and resource with explicit scope: 'Copy a campaign with its ad squads (and optionally ads) into a NEW campaign.' The 'NEW campaign' emphasis and the squad-level option distinguish it from a squad-only copy or a bare create, so an agent can identify the operation without opening the schema.

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?

Gives a clear operational context: preview first, review in Ads Manager, then enable with snap_set_status. It names the follow-up tool and the confirm/approval_token flow, but does not explicitly state when to prefer this over snap_copy_adsquad or snap_create_campaign.

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