Skip to main content
Glama

ads_update_sp_campaign

Destructive

Aggiorna una o PIÙ campagne SP. SINGOLA: campaign_id + patches (patches.daily_budget numero → convertito nel payload v3 budget{budgetType:DAILY,budget}; patches.state ENABLED|PAUSED; patches.placement_bidding = MOLTIPLICATORI per placement [{placement, percentage 0-900}] con placement PLACEMENT_TOP|PLACEMENT_REST_OF_SEARCH|PLACEMENT_PRODUCT_PAGE|SITE_AMAZON_BUSINESS (alias top/rest_of_search/product_page/business); patches.bidding_strategy LEGACY_FOR_SALES|AUTO_FOR_SALES|MANUAL|RULE_BASED). Flusso placement: execute_sql su fact_campaign_placement_daily (performance per placement) → ads_list_sp_campaigns (placement_adjustments attuali) → anteprima prima→dopo → conferma → questo tool; esito verificato per placement (read-after-write). BATCH (consigliato per agire su più campagne in una volta, es. "sistema 10 campagne"): items=[{campaign_id, daily_budget?, state?, placement_bidding?}], ogni campagna con valori diversi, MAX 25. Esito verificato per-id (budget e/o stato). I SEGMENTI DI PUBBLICO non si toccano qui (usa ads_update_sp_audience_bidding): quando cambi placement o strategia il tool rilegge la campagna e mantiene i segmenti esistenti.

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": "ads_update_sp_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoBatch: [{campaign_id, daily_budget?, state?, placement_bidding?}], max 25
patchesNoCampi da modificare (solo quelli indicati): es. state, daily_budget, dynamic_bidding.
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
confirm_idNoToken di conferma ritornato dall'anteprima. Ripassa lo STESSO payload + confirm_id per eseguire davvero la scrittura.
profile_idNoAmazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost.
campaign_idNoId campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • addedInput schema / properties / campaign_id / description
      Added value: +"Id campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns)."
    • addedInput schema / properties / items / items / properties / campaign_id / description
      Added value: +"Id campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns)."
    • addedInput schema / properties / items / items / properties / daily_budget / description
      Added value: +"Budget giornaliero in valuta del marketplace, es. 15."
    • addedInput schema / properties / items / items / properties / placement_bidding / description
      Added value: +"Modifiche bid per posizionamento: array di { placement, percentage }."
    • addedInput schema / properties / items / items / properties / placement_bidding / items / properties / percentage / description
      Added value: +"Variazione percentuale del bid come intero, es. 50 = +50%."
    • addedInput schema / properties / items / items / properties / placement_bidding / items / properties / placement / description
      Added value: +"Posizionamento: PLACEMENT_TOP (primo risultato), PLACEMENT_REST_OF_SEARCH, PLACEMENT_PRODUCT_PAGE."
    • addedInput schema / properties / items / items / properties / state / description
      Added value: +"Stato: ENABLED, PAUSED oppure ARCHIVED (maiuscolo; ARCHIVED è irreversibile)."
    • addedInput schema / properties / patches / description
      Added value: +"Campi da modificare (solo quelli indicati): es. state, daily_budget, dynamic_bidding."
    • addedInput schema / properties / patches / properties / bidding_strategy / description
      Added value: +"Strategia di bidding della campagna, es. LEGACY_FOR_SALES, AUTO_FOR_SALES, MANUAL."
    • addedInput schema / properties / patches / properties / budget / description
      Added value: +"Budget della campagna: oggetto con l'importo giornaliero, es. { \"budget\": 15 }."
    • addedInput schema / properties / patches / properties / daily_budget / description
      Added value: +"Budget giornaliero in valuta del marketplace, es. 15."
    • addedInput schema / properties / patches / properties / dynamicBidding / description
      Added value: +"Strategia di bidding dinamico (formato SB), es. { \"bidOptimization\": true }."
    • addedInput schema / properties / patches / properties / placement_bidding / items / properties / percentage / description
      Added value: +"Variazione percentuale del bid come intero, es. 50 = +50%."
    • addedInput schema / properties / patches / properties / placement_bidding / items / properties / placement / description
      Added value: +"Posizionamento: PLACEMENT_TOP (primo risultato), PLACEMENT_REST_OF_SEARCH, PLACEMENT_PRODUCT_PAGE."
    • addedInput schema / properties / patches / properties / profile_id / description
      Added value: +"Amazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost."
    • addedInput schema / properties / patches / properties / state / description
      Added value: +"Stato: ENABLED, PAUSED oppure ARCHIVED (maiuscolo; ARCHIVED è irreversibile)."
    • addedInput schema / properties / profile_id / description
      Added value: +"Amazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds behavior the annotations cannot: a preview-then-confirm handshake requiring the SAME payload plus confirm_id, a 25-item batch ceiling, read-after-write verification per placement and per id, and the guarantee that existing audience segments are re-read and preserved when placement or strategy changes. These are consequential, non-obvious traits that materially change how an agent invokes the tool.

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?

Front-loaded and organized by explicit SINGOLA / BATCH / placement-flow markers, so an agent can scan to the relevant section. It is dense and unbroken prose with parenthetical chains, so it is near the upper bound of useful length for a dual-mode tool, but almost every clause carries operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, nested, dual-mode mutation tool with no output schema, the description covers everything needed to call it correctly: mode selection, field-level semantics, the confirm flow, batch limits, verification expectations, and what this tool deliberately does not touch. Nothing essential is left to inference.

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?

Adds substantial meaning beyond a 100%-covered schema: it documents the number→v3 budget{budgetType:DAILY,budget} conversion, the placement aliases (top/rest_of_search/product_page/business) and the 0-900 percentage range, and the items[] shape with max 25. The one gap is that it lists patches.state as only 'ENABLED|PAUSED' while the schema enum also permits ARCHIVED (irreversible), a minor mismatch that could mislead an agent relying on the prose.

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?

Opens with a specific verb+resource ('Aggiorna una o PIÙ campagne SP') and immediately splits the tool into its two distinct operating modes (SINGOLA vs BATCH), so an agent knows exactly what surface it covers. It also names the sibling it is NOT (ads_update_sp_audience_bidding for audience segments), making it distinguishable from the other ads_update_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly recommends batch for acting on multiple campaigns ('consigliato ... es. sistema 10 campagne'), describes the prerequisite chain for the tricky placement case (execute_sql on fact_campaign_placement_daily → ads_list_sp_campaigns → preview → confirm → this tool), and states the exclusion: audience segments are handled by ads_update_sp_audience_bidding. When-to-use, when-to-use-something-else, and the ordering of steps are all present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources