Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_bulk_set_schedule

Destructive

Set start and end times for up to 20 campaigns or ad squads, with a preview step and approval token before applying changes.

Instructions

Set start/end time on up to 20 campaigns or ad squads. Changes that let ACTIVE items deliver sooner are checked and limited like enabling them. 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>",
      "ids": "<ids>"
    },
    "name": "snap_bulk_set_schedule"
  }
}

Input Schema

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

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds genuinely new behavior: results are preview-only unless confirm=true, an approval_token must be replayed with identical arguments to apply, and changes that let ACTIVE items deliver sooner are checked and limited like status enables. The missing piece is what a preview returns beyond the token.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: scope first, the guard rule second, the approval workflow last. Dense but every sentence carries information; minor cost is that the two-step flow is packed into one long sentence.

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 bulk mutation with no output schema and partial schema coverage, the description covers the riskiest behavior (two-phase confirmation and approval token) well. Gaps remain on time value format and preview response contents, but an agent can call it safely without them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, so the description carries weight: it explains confirm and approval_token semantics (token must come from the preview of this exact request) and confirms the 20-item ceiling. It says nothing about start_time/end_time format, timezone, or the campaign/adsquad enum, leaving the two time parameters undocumented anywhere.

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 a specific verb and resource with explicit scope: 'Set start/end time on up to 20 campaigns or ad squads.' The batch size and the entity types make it distinguishable from a single-entity schedule setter, though it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives strong procedural guidance for the preview-then-apply flow, which tells the agent how to use it. It does not say when this tool is preferred over the single-entity schedule setter or what happens if an id is invalid or belongs to another entity type.

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