Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_bulk_rename

Destructive

Find and replace text in names of up to 20 Snapchat campaigns, ad squads, or ads; preview changes first and apply with an approval token.

Instructions

Find-and-replace inside the names of up to 20 campaigns, ad squads or ads. 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>",
      "find": "<find>"
    },
    "name": "snap_bulk_rename"
  }
}

Input Schema

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

Annotations already flag destructiveHint, non-idempotent and openWorld, so the safety bar is lower. The description still adds meaningful context beyond them: the dry-run default, the 20-item cap, and the exact token-round-trip required to apply. It stops short of describing name-collision behavior or partial-failure handling across 20 ids.

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 sentences, front-loaded with purpose then the safety contract. Every clause carries information an agent needs: scope, dry-run default, and the two-step token flow.

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?

A destructive, non-idempotent bulk mutation with no output schema, and the description covers what matters most: preview output includes an approval_token, and the same arguments must be repeated with confirm=true. Missing only edge-case behavior such as what happens when some ids fail.

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 description coverage is 33%, so the description must compensate, and it does for the riskiest params: confirm's preview/apply semantics, approval_token's provenance, and the 20-element limit on ids. The replace parameter's default of empty string (effectively deleting the matched text) is never explained, which is the one real gap.

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: find-and-replace on names of campaigns, ad squads, or ads, with an explicit 'up to 20' scope. The bulk/multi-entity framing implicitly distinguishes it from the singular snap_rename, though it never names that sibling.

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 procedural guidance: previews unless confirm=true, and a required two-step sequence with approval_token. It does not say when to prefer snap_rename over this tool or what to do if the token is stale, but the when/how of the workflow is unambiguous.

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