Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_set_bid_strategy

Destructive

Switch a Snapchat ad squad between max bid and target cost strategies by setting a new bid, with preview and approval-token confirmation before applying changes.

Instructions

Switch an ad squad between max bid (LOWEST_COST_WITH_MAX_BID) and target cost (TARGET_COST), with the bid for the new strategy. An ad squad on auto-bid may be switched to one of these (it adds a bid cap). Switching TO auto-bid is not offered because it would remove the bid cap. The bid follows the same limits as snap_set_bid (absolute SNAP_MAX_BID, +50% per step and per 24 hours). 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>",
      "strategy": "<strategy>",
      "bid": "<bid>"
    },
    "name": "snap_set_bid_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
bidYesAccount currency: the max bid, or the target cost
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
strategyYes
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.7/5.0
Behavior5/5

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

Substantively exceeds the annotations (destructiveHint=true, openWorldHint=true, idempotentHint=false) by disclosing the two-step preview/approval_token contract, that nothing is sent until confirm=true, the +50% per-step and per-24-hour bid ceilings, and the SNAP_MAX_BID absolute cap. It also explains a non-obvious consequence of the mutation (switching to auto-bid would drop the bid cap), which is exactly the kind of behavioural risk the annotations cannot convey.

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?

Four tight sentences, front-loaded with the core action, then the eligibility restriction, then the bid limits, then the two-step protocol. No filler and no restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description still explains what the preview returns (a preview plus an approval_token) and how to complete the mutation, which is the critical missing piece for a destructive, non-idempotent write. Given five parameters and a preview/confirm flow, nothing an agent needs in order to call this correctly is absent.

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?

At 60% schema coverage the description adds real meaning: it clarifies that 'bid' is interpreted as the max bid or the target cost depending on strategy, and documents the ordering/identity constraint that the apply call must repeat the exact same arguments with the returned approval_token. The bid limits are stated in prose; the enum values and confirm semantics largely duplicate the schema.

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 ('Switch an ad squad between max bid ... and target cost') and names the exact enum values involved. It also disambiguates from the identically-named sibling by noting the bid is set 'for the new strategy', so an agent can tell this apart from snap_set_bid.

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 a clear when-to-use rule plus a meaningful exclusion: 'Switching TO auto-bid is not offered because it would remove the bid cap', and notes auto-bid squads may move into these strategies with an added bid cap. The relationship to snap_set_bid is only implied through the shared bid limits rather than stated as an explicit 'use that tool when you only want to change the bid'.

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