Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_upload_media

Upload a local image or video file of up to 1 GB to your Snapchat ad account as a standalone media asset. Preview first, then confirm with an approval token to apply, and poll until READY.

Instructions

Upload a local video (.mp4/.mov) or image (.jpg/.png), up to 1 GB (files over 32 MB go in chunks), to the ad account. It is not attached to any ad. Then poll snap_get_media until READY and use snap_create_creative. Previews (file 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": {
      "file_path": "<file_path>"
    },
    "name": "snap_upload_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
file_pathYesAbsolute path on this machine
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.5/5.0
Behavior4/5

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

With annotations present, the description adds substantial context beyond them: file-size thresholds (32 MB chunking, 1 GB ceiling), the fact that confirm=false performs only a file check and sends nothing, and that the preview returns an approval_token that must be echoed with identical arguments to apply. It does not address what happens on repeated uploads of the same file (consistent with idempotentHint=false) or partial-failure behavior during chunked uploads, so it stops short of full disclosure.

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?

Dense and mostly front-loaded: scope and constraints first, then the downstream workflow, then the confirm/approval mechanics. The two-step preview explanation is split awkwardly across the last two sentences, repeating 'confirm=true' and 'approval_token', but no sentence is genuinely 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 mutation tool with no output schema, it covers the essentials an agent needs: what the preview returns, how to apply it, formats, and size limits. It leaves out what the applied upload returns (e.g., how the new media is identified for the subsequent snap_get_media poll) and any failure semantics, which are the remaining gaps.

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 75% and the schema already documents confirm, approval_token, and file_path, but the description adds real meaning: accepted extensions and the size limits that determine chunking behavior for file_path, plus the requirement to reuse the exact same arguments with the same approval_token. The 'name' parameter is left unexplained in both schema and description, which keeps this from a 5.

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 (upload a local video/image to the ad account), enumerates accepted formats and the 1 GB cap, and explicitly distinguishes itself from related tools by saying the media 'is not attached to any ad' and that snap_create_creative comes after. An agent can tell exactly what this does versus snap_create_creative without opening a 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?

Gives an explicit ordered workflow: upload, then poll snap_get_media until READY, then call snap_create_creative. It also states a negative condition (not attached to any ad), which prevents the agent from expecting a creative to be produced here.

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