Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_create_ad

Preview and create a paused Snapchat ad from an existing creative in an ad squad, requiring an approval token before changes apply.

Instructions

Create an ad from an existing creative inside an ad squad. The ad type follows the creative (WEB_VIEW -> REMOTE_WEBPAGE, SNAP_AD -> SNAP_AD, COMPOSITE Story -> STORY, COLLECTION -> COLLECTION); give ad_type only for other formats. Always created PAUSED. 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>",
      "adsquad_id": "<adsquad_id>",
      "name": "<name>"
    },
    "name": "snap_create_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
ad_typeNoNormally left out: it is taken from the creative
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
adsquad_idYes
creative_idYes
approval_tokenNoThe approval_token returned by the preview of this exact request. Required with confirm=true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.2/5.0
Behavior3/5

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

Adds real behavior beyond the annotations: the tool is non-idempotent (implied by the approval_token requirement), always creates PAUSED, and is preview-first unless confirm=true. That is genuinely useful context the annotations do not supply. However, there is no mention of permission or auth requirements for an open-world write to an ad account, and no detail on what the preview returns beyond the token.

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?

Dense, front-loaded, and every clause carries information: the type mapping, the PAUSED default, and the two-step protocol in four sentences. The parenthetical enumeration of creative-to-adtype mappings is compact rather than wasteful.

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 write tool with no output schema, it covers the mutation semantics, the dry-run default, and the required return artifact (approval_token from the preview). Missing only edge behavior: whether the token expires, and what happens if a previewed creative changes before confirm.

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?

With 50% schema description coverage and six parameters, the description compensates well: it explains that ad_type is normally omitted and derived, and that confirm/approval_token form a matched pair where the token must come from the preview of the identical request. Only name and the id patterns 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 ('Create an ad from an existing creative inside an ad squad') plus the scope constraint that the creative determines the ad type. The CREATE-tool siblings (snap_create_creative, snap_clone_ad, snap_ad_preview) are distinguishable because this one requires an existing creative and an adsquad.

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 explicit conditional guidance: supply ad_type only for formats outside the WEB_VIEW/SNAP_AD/COMPOSITE Story/COLLECTION mapping, and expect PAUSED. It also prescribes the exact two-step apply protocol. It stops short of naming an alternative path, but no sibling is misrepresented.

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