Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_create_collection_creative

Creates a Collection Ad creative from a main image or video plus 4-20 linked product tiles; returns a preview and approval token before applying changes.

Instructions

Create a Collection Ad creative: a main image or video plus 4-20 product tiles, each a square image (1:1, at least 120x120 px) that opens its own https page, and a fallback page for a swipe on the main Snap. Creates the product tiles, the row that holds them and the COLLECTION creative; nothing delivers. Use the returned creative with snap_create_ad (ad type COLLECTION). 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": {
      "name": "<name>",
      "top_snap_media_id": "<top_snap_media_id>",
      "headline": "<headline>",
      "fallback_url": "<fallback_url>",
      "products": "<products>"
    },
    "name": "snap_create_collection_creative"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
headlineYesMax 34 characters
productsYes
profile_idNo
button_labelNoLabel of the product rowSHOP_NOW
fallback_urlYeshttps:// page opened by a swipe on the main Snap
approval_tokenNoThe approval_token returned by the preview of this exact request. Required with confirm=true.
top_snap_media_idYesThe main image or video (READY)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior, but the description adds substantially more: it creates three distinct entities (product tiles, the row, the COLLECTION creative), it explicitly does not deliver anything, and it defines a preview/approval-token safety gate. That is exactly the operational context the annotations cannot convey.

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 definition, then the side-effect scope, then the follow-up tool, then the confirm workflow. Slightly redundant in that 'Previews unless confirm=true' and the 'Two steps' sentence restate the same gate, but the density is justified for a nine-parameter creative builder.

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 nine-parameter, non-idempotent mutation with no output schema, the description covers the key gaps: what is created, what is not delivered, and how the preview-to-apply transition works. The main remaining hole is profile_id (undocumented in schema and description) and no note on what the preview response contains beyond the approval_token.

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 67% schema coverage, the description still adds real meaning beyond the schema: the 4-20 tile cardinality, 1:1 square images at minimum 120x120 px, each tile opening its own https page, and the fallback page being what a swipe on the main Snap opens. It does not explain profile_id or the name parameter, which remain undocumented in both places.

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 a Collection Ad creative') and immediately defines the composition: a main image or video plus 4-20 product tiles with a fallback page. It also distinguishes itself from the delivery-side sibling by naming snap_create_ad and specifying ad type COLLECTION, so an agent can tell it apart from snap_create_creative or snap_create_story_creative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'Use the returned creative with snap_create_ad (ad type COLLECTION)' names the follow-up tool and the required ad type. It also gives the precise two-step protocol (confirm=false for preview plus approval_token, then repeat identical arguments with confirm=true) and states 'nothing delivers', so there is no ambiguity about when and how to use it.

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