Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_set_status

Destructive

Pause or enable Snapchat campaigns, ad squads, or ads with a preview-first, approval-token workflow that checks budget limits before applying changes.

Instructions

Pause (PAUSED) or enable (ACTIVE) a campaign, ad squad or ad. Enabling shows the daily budget that would really start delivering (including the ACTIVE ad squads under a campaign) and is refused above the configured limits. Previews unless confirm=true. Never deletes. 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>",
      "status": "<status>"
    },
    "name": "snap_set_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
entityYes
statusYes
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
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.1/5.0
Behavior4/5

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

Beyond the annotations it discloses the two-step preview/approval_token protocol, the refusal condition on enable, and that enabling surfaces the real deliverable daily budget including ACTIVE ad squads. 'Never deletes' usefully scopes the destructiveHint so the agent understands the mutation is status/budget affecting, not a removal. It omits any statement about idempotency or repeat-call effects, which the annotations mark as non-idempotent.

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 action and entities, then guardrails, then the safety statement, then the two-step mechanics. No filler or restated title.

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 mutation with no output schema and partial schema coverage, it explains the return of the preview step (approval_token) and the safety gate, which is the critical information. It could say more about what the preview body contains besides the token, but nothing essential to correct invocation is missing.

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?

With only 40% schema coverage, the description carries real weight: it explains the confirm preview-vs-apply meaning and the required pairing of confirm=true with an approval_token from the matching preview. The entity/status parameters are covered by enums and the description's PAUSED/ACTIVE mapping, leaving only minor implicit details.

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 names the concrete verb+resource: pause (PAUSED) or enable (ACTIVE) a campaign, ad squad or ad, and ties the enum values to real intent. The singular scope ('a campaign, ad squad or ad') implicitly separates it from snap_set_status_bulk, though that sibling is never named.

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 gives clear operating context: enabling is refused above configured limits, and the tool previews unless confirm=true. It does not explicitly direct the agent to a bulk alternative or to related budget tools, so the when-to-use-this-vs-sibling guidance is incomplete rather than absent.

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