Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_rename

Destructive

Preview and apply new names for a Snapchat campaign, ad squad, or ad. Use a two-step approval token flow so changes are confirmed before they take effect.

Instructions

Rename a campaign, ad squad or ad. 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>",
      "new_name": "<new_name>"
    },
    "name": "snap_rename"
  }
}

Input Schema

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

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

Annotations already flag destructiveHint=true, non-idempotent and open-world, so the safety profile is partly covered. The description adds meaningful context beyond them: the call is preview-by-default and nothing is sent until confirm=true with a matching approval_token, which materially changes how an agent sequences the call. It doesn't state permissions required or that renaming preserves entity ID, so not a 5.

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 short sentences, front-loaded with the purpose, then the default behavior, then the exact two-step procedure. Every sentence carries operational information and nothing is repeated.

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 two-step mutation with no output schema, the description covers what an agent most needs: the preview requirement, the token handoff, and the fact that the preview returns an approval_token. Only permission requirements and the immutability of the entity ID are left implicit.

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 40%, so the description needs to compensate. It does explain the confirm/approval_token coupling clearly, but those two are already the schema-documented parameters; entity values, the id pattern, and the new_name minimum length remain undocumented in the description. Adequate baseline rather than value-add.

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?

Opens with a specific verb and the exact resource set: 'Rename a campaign, ad squad or ad.' An agent can immediately tell this is a single-entity rename, implicitly distinct from a bulk operation. It stops short of naming a sibling tool, so it lands at 4 rather than 5.

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 explicit when-to-use guidance for the two modes: confirm=false for preview, confirm=true to apply, and how to repeat the call. It does not address when to prefer this over a bulk rename sibling, but the operational routing within the tool 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