Skip to main content
Glama
saadsh0

Snapchat Ads MCP Server

by saadsh0

snapchat_update_campaign_budget

Update a Snapchat campaign's daily budget or lifetime spend cap to control ad spend. Automatically clears cached data after the update.

Instructions

Update the daily budget or lifetime spend cap of a campaign. $1 = 1,000,000 micro-dollars. Example: $50/day = 50000000. Automatically clears cached data for the account after the update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations indicate the tool is not read-only and not destructive. The description adds that it 'automatically clears cached data', a behavioral side effect not captured by annotations. No contradictions.

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?

Two sentences: first states the core action, second provides a conversion example and side effect. No superfluous words, efficiently front-loaded.

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?

With an output schema present, return values need not be described. The description covers the primary action and a key side effect. However, it does not clarify whether both daily_budget_micro and lifetime_spend_cap_micro can be updated simultaneously.

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?

The input schema already provides descriptions for each parameter (e.g., micro-dollar conversion). The description briefly reiterates the conversion example but adds no new semantic meaning beyond what the schema conveys.

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 states the verb 'Update' and the resource 'daily budget or lifetime spend cap of a campaign', distinguishing this tool from sibling tools like snapchat_update_status that update campaign status.

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?

The description provides a conversion example for micro-dollars, aiding correct usage. However, it does not explicitly state when to use this tool versus alternatives (e.g., update_status), nor does it mention constraints like setting at least one budget field.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/saadsh0/snapchat-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server