Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_copy_adsquad

Copy an ad squad, optionally with its ads, into a target campaign as paused with scaled budgets. Preview first, then confirm with the returned approval token to apply.

Instructions

Copy one ad squad (optionally with its ads) into a target campaign. Created PAUSED. Budgets are scaled by budget_scale and must stay within the configured limits. Previews unless confirm=true. 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": {
      "adsquad_id": "<adsquad_id>",
      "target_campaign_id": "<target_campaign_id>"
    },
    "name": "snap_copy_adsquad"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
new_nameNo
adsquad_idYes
include_adsNo
budget_scaleNo
approval_tokenNoThe approval_token returned by the preview of this exact request. Required with confirm=true.
target_campaign_idYes

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?

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses the created entity's state (PAUSED), an enforced constraint on budget scaling, and a mandatory two-step preview/approval workflow. These are exactly the behavioral facts an agent needs before committing a write operation.

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?

The description is front-loaded with the action and target, then the state, then the workflow, with no filler. The final sentence restates the confirm/approval_token mechanics that the schema properties already describe, which is mild redundancy but justified for a two-step safety protocol.

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?

With no output schema, the description still conveys the essential contract: what is created, in what state, under what budget constraints, and how preview versus apply differ. It stops short of describing what the preview payload contains besides the token and leaves new_name unexplained, but nothing critical for a correct invocation is missing.

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 only 29%, so the description must carry meaning, and it does for most parameters: budget_scale is described as scaling budgets subject to configured limits, include_ads as pulling the squad's ads along, and the confirm/approval_token pairing as a preview-then-apply gate. The only gap is new_name, which is undocumented in both the schema and the description.

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 opening sentence states a specific verb and resource ('Copy one ad squad') plus the destination ('into a target campaign'), and the parenthetical clarifies the optional ad payload. This cleanly separates it from the sibling snap_copy_campaign, which operates on a campaign rather than an ad squad.

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?

The description tells the agent exactly when and how to invoke it: preview first with confirm=false, then repeat the identical arguments with confirm=true and the returned approval_token. It does not explicitly contrast with snap_copy_campaign or snap_clone_ad, but the resource-level scoping makes the intended use clear.

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