Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_set_bid

Destructive

Set the maximum bid for a Snapchat ad squad that uses max bidding, with safety-limit checks and preview/approval before applying changes.

Instructions

Set the max bid (account currency) on an ad squad that uses a max bid. Refused above the absolute limit (SNAP_MAX_BID), above +50% per step and per 24 hours (SNAP_MAX_BID_INCREASE_PCT), and on auto-bid squads. 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>",
      "bid": "<bid>"
    },
    "name": "snap_set_bid"
  }
}

Input Schema

NameRequiredDescriptionDefault
bidYes
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.6/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/non-idempotent, and the description adds substantial context beyond them: the exact refusal thresholds, the fact that nothing is sent unless confirm=true, and the approval_token handshake required to apply. This is precisely the mutation-safety detail an agent needs.

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 dense sentences, front-loaded with the operation, then the refusal rules, then the workflow. No filler; every clause carries operational meaning.

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 no output schema, the description still explains that a preview returns an approval_token and that the same arguments must be repeated with confirm=true. Complete enough to call correctly, though it does not state what else the preview response contains (e.g., resulting bid or validation detail).

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 50% (bid and adsquad_id are undocumented in the schema), and the description compensates by specifying that bid is in account currency and is a max bid, and by explaining the confirm/approval_token pairing. It still does not describe the adsquad_id format or the units/range of bid beyond the schema's exclusiveMinimum.

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 ('Set the max bid ... on an ad squad') plus the scope qualifier 'that uses a max bid', which implicitly separates it from auto-bid squads and from the sibling snap_set_bid_strategy. An agent can identify the operation and its applicability without opening the schema.

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 explicit when-not conditions (auto-bid squads, above SNAP_MAX_BID, above +50% per step/24h) and a clear two-step preview-then-confirm procedure. It does not name a sibling alternative for the auto-bid case, so it falls just short of full routing 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