Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_bulk_set_budget

Destructive

Update daily budgets for up to 20 ad squads at once in set or scale mode, previewing changes and requiring approval before applying them.

Instructions

Change the daily budget of up to 20 ad squads at once: mode 'set' (same value for all) or 'scale' (multiply each, e.g. 0.5 = half). Every item keeps the single-item guards (absolute limit, max +100% per step and per 24 hours, minimum budget). 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_ids": "<adsquad_ids>",
      "mode": "<mode>",
      "value": "<value>"
    },
    "name": "snap_bulk_set_budget"
  }
}

Input Schema

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

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

The annotations already disclose the important safety profile (destructiveHint=true, readOnlyHint=false, idempotentHint=false, openWorldHint=true), so the description's main added value is the guard set: absolute limit, max +100% per step and per 24 hours, and a minimum budget per item. That is genuinely useful pre-call context on limits. However, it does not say what happens if some of the 20 items fail, whether the batch is atomic, or whether re-running a consumed approval_token errors, which are the residual behavioral questions for a destructive bulk write.

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 scope and modes in one sentence, then the guards, then the two-step confirm flow in the order an agent needs them. No filler or marketing tone; every sentence carries a distinct constraint.

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 destructive batch mutation with no output schema, the description covers limits, modes, and the preview/apply protocol well enough to call it correctly. The remaining gap is result semantics: whether the preview lists per-item outcomes and how partial failures are reported, which an agent would want before applying changes to 20 squads.

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 40%, and the description compensates well: it defines the two mode values, gives a concrete example for 'scale' (0.5 = half), and restates the 20-item cap. It clarifies the preview/apply pairing for confirm and approval_token, including that the token must come from the preview of that exact request. It says little about how 'value' is interpreted per mode beyond the parenthetical, but the mode sentence covers the interpretative gap adequately.

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 concrete verb and resource ("Change the daily budget of up to 20 ad squads at once") plus the batch scope, which separates it from the single-item snap_set_daily_budget sibling without ambiguity. The two operating modes ('set' vs 'scale') are named in the same opening sentence, so an agent can classify the tool immediately.

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?

Explains the two-step workflow precisely: confirm=false previews and returns an approval_token, then repeat the identical arguments with confirm=true to apply. It also explains when to pick each mode (same value for all vs multiply each). Nothing is said about when to prefer this over the single-ad-squad tool or when to fall back to it for a small number of items, which keeps it off 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