Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_create_pixel_audience

Create a Snapchat pixel audience from users who fired chosen events (e.g., ADD_CART or VIEW_CONTENT) within a retention window; preview it first, then apply with an approval token.

Instructions

Create an audience of people who fired pixel events (e.g. ADD_CART or VIEW_CONTENT) within N days. Audience only, nothing is delivered. Pixel defaults to SNAP_PIXEL_ID. 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>",
      "events": "<events>"
    },
    "name": "snap_create_pixel_audience"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the preview/confirm two-phase commit, the approval_token round-trip, and the pixel_id default. It stops short of stating rate limits, permission requirements, or what the preview payload contains.

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?

Four tight sentences, front-loaded with purpose, then scope exclusion, then the two-step workflow. Every sentence carries information; the only minor cost is that the confirm/approval_token mechanics are stated twice (once in prose, once implicitly in the schema).

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 6-parameter mutation tool with no output schema, the description covers the critical operational facts: nothing is delivered, previews are the default, and applying requires repeating the call with confirm=true plus the token. Missing only the unmentioned 'name' parameter and any note on what the preview returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, so the description must compensate, and it does for most parameters: events (with examples), retention_days ('within N days'), pixel_id default, confirm, and approval_token. However, the required 'name' parameter is never mentioned and no format or constraint detail is added beyond the schema, so it lands at baseline rather than above it.

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 audience of people who fired pixel events') plus the qualifying dimension (within N days). The clause 'Audience only, nothing is delivered' separates it from the ad/creative creation siblings, so an agent can route correctly without opening the schema.

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 when-to-use context (pixel-event audiences, retention window) and an explicit when-not ('Audience only, nothing is delivered'). It does not name a sibling alternative such as snap_create_lookalike for related audience types, which keeps it short of a 5.

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