Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_influencer_batch

Claim up to 10 Snapchat influencer ad codes and create paused ads in one ad squad, with preview and approval before applying; expired codes are skipped and reported.

Instructions

Influencer flow for up to 10 ad codes into one ad squad: for each, claim, wait for media, create creative, create a PAUSED ad. Expired codes are skipped and reported, others continue. Stops if a claimed code ends up incomplete. Claiming is one-way. Previews (format check only) 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>",
      "items": "<items>",
      "headline": "<headline>",
      "url": "<url>"
    },
    "name": "snap_influencer_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
itemsYes
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
headlineYes
adsquad_idYes
profile_idNo
approval_tokenNoThe approval_token returned by the preview of this exact request. Required with confirm=true.
call_to_actionNoSHOP_NOW

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?

Adds substantial behavior beyond annotations: irreversibility ("claiming is one-way"), partial-failure semantics (report expiry, continue; otherwise halt on incomplete claims), and the approval_token gate. However, with annotations already declaring destructiveHint=false, idempotentHint=false and openWorldHint=true, the description leaves gaps on permissions and on what the applied run actually reports back per code. Solid value but not exhaustive.

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 workflow, then failure handling, then the preview/confirm mechanics, with no filler sentences. It is dense but every clause carries information; slightly better segmentation of the failure and confirmation rules would improve scannability.

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?

With 8 parameters, only 25% schema coverage, and no output schema, the description does the heavy lifting on flow and failure behavior and even states what the preview returns (a preview plus approval_token). It falls short on the creative-field parameters and on what a successful apply returns beyond the expiry report.

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 description coverage is only 25% and the description compensates for part of it: it explains the items/ad_code batch (up to 10), confirm, and approval_token semantics including the requirement to reuse the exact same arguments. It says nothing about adsquad_id, headline, url, call_to_action, or profile_id, leaving half the parameters unexplained in both the schema and the description.

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 multi-step verb chain and resource: batch influencer flow for up to 10 ad codes into one ad squad (claim → wait for media → create creative → create PAUSED ad). The batch framing plus the enumerated stages makes it distinguishable from single-item siblings such as snap_claim_ad_code and snap_create_creative without opening their schemas.

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 operational guidance on the preview/apply two-step flow (confirm=false returns preview plus approval_token; repeat the same arguments with confirm=true to apply) and on edge cases (expired codes skipped and reported, stop if a claimed code is incomplete). It does not explicitly contrast with sibling tools like the single-influencer flow, but the usage conditions for this tool are clear.

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