Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_set_schedule

Destructive

Set or update start and end times for a Snapchat campaign or ad squad, with preview and approval-token confirmation before applying scheduled delivery changes.

Instructions

Set start_time and/or end_time (ISO with offset) on a campaign or ad squad. end_time must be in the future and after the start. A change that lets an ACTIVE item deliver sooner (an earlier start, or reviving an ended item) is checked and limited like enabling it. 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>"
    },
    "name": "snap_set_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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

A4.3/5.0
Behavior4/5

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

Beyond the annotations (destructive, non-readonly), the description details specific business limitations, such as constraints on changes that enable active items to deliver sooner, which is crucial behavioral knowledge.

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?

The description is dense, but it uses its structure to group related information effectively: parameters, constraints, and the multi-step workflow. Every sentence provides unique functional value.

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?

The definition is highly complete for invocation. It covers all necessary prerequisites, constraints, and the entire operational flow required by the agent to execute the tool correctly.

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?

Given the low schema coverage (33%), the description is necessary. It provides semantic meaning to the time parameters (ISO with offset) and clarifies the functional roles of the `confirm` and `approval_token` parameters within the overall workflow.

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?

The description clearly identifies the specific action ("Set start_time and/or end_time") and the resource affected ("campaign or ad squad"), providing maximal specificity and distinction from other sibling tools.

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

Usage Guidelines5/5

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

It provides critical usage guidance by detailing a mandated two-step process: first, using `confirm=false` to get an `approval_token`, and then using `confirm=true` with that token to apply the changes.

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