Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_budget_advice

Read-only

Compare active ad squads by ROAS to receive read-only suggestions for lowering underperformers and raising proven ones within limits, funded by freed budget plus optional extra daily budget.

Instructions

Where could budget move? (read-only suggestions; nothing is changed) Compares ACTIVE ad squads that have a daily budget by ROAS over the last days. Suggests lowering the ones far under the median (-25%) and raising the proven ones (+20%, never above the configured limits), funded by what is freed, plus optional extra_budget per day. Each suggestion names the tool that applies it, which previews and waits for your approval.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "snap_budget_advice"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
min_spendNo
extra_budgetNoExtra daily budget you are willing to add, in account currency

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 readOnlyHint=true, but the description goes well beyond them: it discloses the comparison basis (ROAS over the last days), the exact adjustment magnitudes (-25% under median, +20% for proven squads), the guardrail (never above configured limits), the funding model (freed budget plus optional extra_budget), and the approval hand-off. These are behavioral traits an agent cannot get from the annotations or schema.

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?

Three sentences, front-loaded with the core question and an immediate read-only disclaimer, then the method and thresholds. The rhetorical opener is redeemed by the parenthetical, and every clause carries information, though the density of the threshold details makes it a slightly heavy read.

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 read-only advisory tool with three optional parameters and no output schema, the definition covers method, thresholds, caps, funding logic, and the follow-up path well. The main omission is the meaning and effect of min_spend, which is left entirely to an undocumented schema property.

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 33%, and the description adds meaning for two of three parameters: 'days' is framed as the ROAS lookback window and 'extra_budget' is described as optional extra daily budget that funds raises. The 'min_spend' parameter is never mentioned in the description, and its schema entry has no description, so that gap remains.

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 definition states a specific analytical action (comparing ACTIVE ad squads with a daily budget by ROAS) and its output form (budget-move suggestions), and the parenthetical '(read-only suggestions; nothing is changed)' separates it from the applying siblings such as snap_set_daily_budget. An agent can tell what it produces and that it does not mutate anything.

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?

It scopes the population clearly (ACTIVE ad squads that have a daily budget) and describes the workflow role: each suggestion names the tool that applies it and that tool previews and waits for approval. It stops short of naming an explicit alternative or stating when NOT to use it, e.g. versus anomaly checking or when a single manual budget change is desired.

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