Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_set_placement

Set a Snapchat ad squad's placements to automatic or custom positions, with preview and approval-token confirmation before applying changes.

Instructions

Choose where on Snapchat an ad squad's ads may appear: automatic (everywhere) or custom positions (PUBLIC_STORIES_INSTREAM, INTERSTITIAL_CONTENT, INTERSTITIAL_SPOTLIGHT, INTERSTITIAL_USER, FEED, CAMERA, CHAT_FEED; CHAT_FEED must come with INTERSTITIAL_CONTENT or INTERSTITIAL_USER). Fewer placements usually mean less reach and a higher cost. Refused on ad squads that use content inclusion or exclusion lists. Undo works when a placement was set before. 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": {
      "adsquad_id": "<adsquad_id>",
      "mode": "<mode>"
    },
    "name": "snap_set_placement"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
positionsNo
adsquad_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.7/5.0
Behavior5/5

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

Annotations already flag a non-read-only, open-world, non-idempotent write, but the description adds the two-step preview/approval_token workflow, refusal conditions, undo availability, and the reach/cost tradeoff. That is substantive behavior beyond the structured fields.

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?

A single dense paragraph, front-loaded with the purpose; the parenthetical enumerations and workflow sentences all carry needed information. Minor run-on feel but no filler.

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 five-parameter mutation with no output schema, the description covers mode selection, position constraints, refusal conditions, undo, and the preview/apply protocol. Missing details like approval_token expiry or required permissions are minor relative to what is provided.

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 only 40% schema description coverage, the description compensates by explaining mode values, all position values, the CHAT_FEED dependency rule, and the confirm/approval_token flow. It does not describe adsquad_id beyond the pattern, but that is a minor gap.

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 ('Choose where on Snapchat an ad squad's ads may appear') and enumerates both modes with all seven position values. An agent can distinguish this from budget, schedule, or targeting siblings 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 Guidelines5/5

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

Explains the automatic vs custom choice, the CHAT_FEED dependency rule, refusal on ad squads with content inclusion/exclusion lists, and the preview/confirm workflow. The conditions that select this tool versus not using it are explicit.

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