Skip to main content
Glama

ads_list_sb_campaigns

Read-only

LIVE: stato corrente delle campagne Sponsored Brands (SB) ESISTENTI (create da Amazon Ads console — Vendooly non crea ancora campagne SB nuove, serve brandEntityId/Brand Registry/asset creativi/moderazione, non implementato). Campi chiave: name, campaignId, state (ENABLED|PAUSED|ARCHIVED), daily_budget, costType (CPC|vCPM), bidding (placement/bidOptimization), brandEntityId. NON ritorna performance: per ACoS/spesa/vendite SB usa execute_sql su fact_campaign_daily (ad_product='SB').

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_list_sb_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
profile_idNoAmazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost.
state_filterNoFiltra per stato: array con ENABLED, PAUSED, ARCHIVED.
campaign_id_filterNoLimita ai soli id campagna indicati (array di stringhe numeriche).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / campaign_id_filter / description
      Added value: +"Limita ai soli id campagna indicati (array di stringhe numeriche)."
    • addedInput schema / properties / profile_id / description
      Added value: +"Amazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost."
    • addedInput schema / properties / state_filter / description
      Added value: +"Filtra per stato: array con ENABLED, PAUSED, ARCHIVED."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, but the description still adds real value by clarifying that data is live/current, that only pre-existing console-created campaigns appear, and that no performance metrics are included. It does not cover pagination or result-size behavior, which keeps it short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the LIVE/existing scope, then key fields, then the performance-metrics exclusion — a logical order with no filler sentences. The parenthetical explanation of why SB campaign creation is unimplemented is slightly verbose but earns its place by preventing a futile write attempt.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the key fields (name, campaignId, state, daily_budget, costType, bidding, brandEntityId). Combined with the explicit non-coverage of performance data and the redirect to execute_sql, an agent has everything needed to call and interpret it.

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 100%, so the schema already documents account_id, profile_id, state_filter and campaign_id_filter. The description reinforces the state vocabulary (ENABLED|PAUSED|ARCHIVED) and the campaignId field, but adds no filtering syntax or default-behavior detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource — listing the current LIVE state of EXISTING Sponsored Brands campaigns — and explicitly scopes out creation ('Vendooly non crea ancora campagne SB nuove'), which separates it from any write-side sibling. It also names the key fields returned, so an agent knows exactly what this tool yields versus ads_list_sd_campaigns or ads_list_sp_campaigns.

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?

Gives an explicit routing rule: use this for SB campaign configuration/state, but for ACoS/spend/sales use execute_sql on fact_campaign_daily with ad_product='SB'. It also states the when-not condition for campaign creation, naming the missing prerequisites (brandEntityId, Brand Registry, creative assets, moderation).

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