Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_set_daily_budget

Destructive

Set a campaign or ad squad daily budget with a preview and approval token; changes apply only after confirmation.

Instructions

Set the daily budget (in account currency, e.g. USD) on a campaign or ad squad. Refused above the absolute limit (SNAP_MAX_DAILY_BUDGET), above the allowed increase per step and per 24 hours (default +100%), and below the minimum. 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": {
      "entity": "<entity>",
      "id": "<id>",
      "daily_budget": "<daily_budget>"
    },
    "name": "snap_set_daily_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
entityYes
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
daily_budgetYes
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?

Beyond the destructive/openWorld annotations, it discloses concrete guardrails the agent cannot infer: an absolute ceiling (SNAP_MAX_DAILY_BUDGET), a per-step and per-24h increase cap (default +100%), and a minimum. It also explains the mutation mechanism itself — preview returns an approval_token that must be replayed with identical arguments — which is exactly the kind of behavior annotations cannot carry.

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?

Three tight sentences, front-loaded with the action and unit, then constraints, then the required call sequence. No filler or restatement of the name.

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 destructive, non-idempotent mutation with no output schema and partial schema coverage, this covers the essential flow and failure conditions. Minor gaps remain: it does not say what a refused request returns (error shape) or exactly what the preview payload contains beyond the 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 40%, so the description has to compensate, and it does for the two non-obvious fields: daily_budget is expressed in account currency, and the approval_token must come from the preview of 'this exact request' and be paired with confirm=true. The id and entity parameters are left to the schema, which is acceptable since entity's enum is self-explanatory.

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?

The description gives a specific verb and resource ('Set the daily budget ... on a campaign or ad squad') and names the unit (account currency, e.g. USD). It does not name a sibling such as snap_bulk_set_budget or snap_budget_advice to distinguish single-entity from bulk use, so it lands 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?

It clearly states when the tool previews versus applies ('Previews unless confirm=true') and spells out the two-step confirm flow. What is missing is guidance on when to reach for this instead of the bulk variant or snap_budget_advice.

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