Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_set_frequency_cap

Sets or clears a frequency cap on an ad squad to control how often one person sees its ads. Previews the change first and applies it only with an approval token and confirm=true.

Instructions

Limit how often one person sees an ad squad's ads: at most count impressions per every HOURS or DAYS (up to 30 days), or clear the cap. A cap lowers repetition (and so frequency), and may lower delivery. Undo works when a cap existed 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>"
    },
    "name": "snap_set_frequency_cap"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoDAYS
clearNo
countNo
everyNo
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
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.3/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false): it discloses the two-step preview/approve protocol, that previews send nothing, that the approval_token must accompany the exact same arguments, the 30-day upper bound, and the undo precondition. Side effects on delivery are called out proactively.

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 the core purpose in the first clause, then layers semantics, side effects, and the confirm protocol in short declarative sentences. No filler; every sentence adds decision-relevant information.

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 non-idempotent, open-world mutation with 7 parameters and no output schema, the description covers the full apply/undo lifecycle and the preview contract. Minor gaps remain around error conditions and what the preview payload contains beyond the approval_token.

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 only 29%, so the description must carry weight and largely does: it defines count as impressions, every as an interval in HOURS or DAYS capped at 30 days, clear as removing the cap, and confirm/approval_token as the preview-apply handshake. Only adsquad_id and the unit default are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Limit how often one person sees an ad squad's ads', including the clear-the-cap variant. An agent immediately knows this is a frequency-cap setter, not a budget/bid/schedule tool. It does not explicitly route away from any sibling, which keeps it at 4 rather than 5.

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 operational context: the cap lowers repetition and may lower delivery, undo only works if a cap previously existed, and the call previews unless confirm=true. It stops short of naming when to prefer an alternative or when not to cap at all, so no explicit exclusion guidance.

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