Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_clone_creative

Duplicate an existing Snapchat creative with a new name and optional headline, link, or call to action while keeping the same media. Preview changes first, then apply them with an approval token.

Instructions

Duplicate a creative with a new name and optionally a new headline, link or call to action (same media). Creatives have no status, so nothing delivers until you attach one to an ad. 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": {
      "creative_id": "<creative_id>",
      "name": "<name>"
    },
    "name": "snap_clone_creative"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
nameYes
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
headlineNo
creative_idYes
approval_tokenNoThe approval_token returned by the preview of this exact request. Required with confirm=true.
call_to_actionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare it is a non-destructive, non-idempotent, open-world write; the description goes well beyond that by disclosing the preview-by-default behavior, the two-step approval_token handshake, and that the duplicated creative has no delivery status until attached to an ad. These are exactly the traits an agent cannot infer from the annotation block.

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?

Four tight sentences: purpose first, then the delivery caveat, then the preview/confirm rule, then the mechanics of the token. Every sentence carries information an agent needs before calling; nothing is padding.

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 7-parameter mutation tool with no output schema, the definition covers the risky parts (preview-first, token reuse, mutation requires confirm=true). It does not say what the applied result returns (e.g. new creative ID) or whether name uniqueness is enforced, but those are secondary given the strong workflow disclosure.

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 description coverage is only 29%, so the description must compensate and largely does: it maps url to "link," names name/headline/call_to_action, and explains confirm and approval_token semantics (token must come from the preview of the same request). Only creative_id is left implicit rather than explained.

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?

States a specific verb and resource ("Duplicate a creative") plus the modifiable fields (name, headline, link, call to action) and the constraint that media is unchanged. This distinguishes it in practice from snap_create_creative, though no sibling is named explicitly.

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 clear operating context: cloning is the right move when reusing existing media, and the caveat that creatives have no status so nothing delivers until attached to an ad tells the agent this is not the last step of a launch. No explicit when-not or named alternative, but the procedural guidance (preview first, then confirm) is concrete.

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