Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_create_campaign

Creates a new paused Snapchat campaign using a preview-and-approval flow, letting you review settings before applying changes and add ad squads afterward.

Instructions

Create a new, empty campaign (always PAUSED, starting shortly after you enable it). Add ad squads with snap_create_adsquad or snap_copy_adsquad. Give catalog_id (objective SALES) for a catalog (Dynamic Product Ads) campaign. 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>"
    },
    "name": "snap_create_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
objectiveNoSALES
catalog_idNoMakes it a catalog campaign; the catalog must belong to the ad account's organization
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.9/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, destructiveHint=false) by disclosing that the created entity is paused, that by default nothing is sent, and that the write requires a two-step preview plus approval_token. It also names a real constraint not surfaced elsewhere: the catalog must belong to the ad account's organization.

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?

Front-loads what is created and its paused state, then layers follow-up tools, the catalog case, and the two-step flow. Every clause carries information; nothing is repeated from the name or restated for padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutation with no output schema, the description covers the safety model (preview/approval_token), the creation semantics (empty, paused), and the sibling tools needed to finish the job. An agent could invoke this correctly without opening the schema.

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 60%, and the description compensates by explaining the catalog_id-to-objective:SALES linkage (catalog/DPA campaigns) and the confirm/approval_token pairing, which the schema documents only mechanically. It does not add anything for 'name' beyond the minLength constraint the schema already carries.

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 new, empty campaign') and pins down the resulting state ('always PAUSED, starting shortly after you enable it'). The word 'empty' plus the pointer to snap_create_adsquad/snap_copy_adsquad distinguishes it from snap_copy_campaign, which would produce a populated campaign.

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 follow-up work to snap_create_adsquad or snap_copy_adsquad, states the condition for supplying catalog_id (objective SALES / Dynamic Product Ads), and explains the preview-vs-apply decision rule with the exact argument that flips it (confirm=true).

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