Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_exclude_segments

Destructive

Add audience segments as EXCLUDE targeting on a Snapchat ad squad while keeping existing targeting; preview changes first, then apply with an approval token and confirm=true.

Instructions

Add audience segments (e.g. past buyers) as EXCLUDE targeting on an ad squad, keeping existing targeting. 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>",
      "segment_ids": "<segment_ids>"
    },
    "name": "snap_exclude_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNofalse = preview only (nothing sent). true = apply; needs approval_token from the preview.
adsquad_idYes
segment_idsYes
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
Behavior5/5

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

Annotations already declare destructiveHint=true and non-readOnly, and the description goes well beyond them by explaining the built-in safety contract: nothing is sent unless confirm=true, and application requires a token from the matching preview. It also discloses the additive behavior ('keeping existing targeting'), which 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?

Three tight sentences, front-loaded with purpose, then the safety gate, then the two-step procedure. No filler and nothing repeated from the schema verbatim.

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?

No output schema exists, and the description covers the key return value (an approval_token) and the default no-op behavior, which is enough to call it safely. It could add what the preview body contains (e.g. reach impact), but nothing critical is missing for correct invocation.

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%, but the description explains the semantics that matter most: confirm's preview/apply duality and the coupling of approval_token to 'this exact request'. adsquad_id and segment_ids are left to their names, though 'e.g. past buyers' clarifies what a segment is.

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?

States a specific verb and resource ('Add audience segments ... as EXCLUDE targeting on an ad squad') and adds scope ('keeping existing targeting'). An agent can tell this is an additive exclusion mutation, though it does not name a sibling such as snap_bulk_exclude_segments to distinguish single vs. bulk use.

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 clear operational guidance for how to invoke: preview by default, and to apply, repeat the same arguments with confirm=true and the returned approval_token. It does not advise when to prefer this over a bulk or alternative segment tool, so exclusions across multiple squads are left to inference.

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