Skip to main content
Glama

ads_list_sp_campaigns

Read-only

LIVE: stato corrente delle campagne SP. Campi chiave per campagna: name, campaignId, state, targetingType (AUTO|MANUAL) e daily_budget = budget giornaliero NUMERICO nella valuta del marketplace (es. 50, 150). NON esiste un "bid" a livello campagna (i bid sono su keyword/target). Usa per VERIFICARE prima di agire o per avere nomi/ID. NON ritorna performance: per ACoS/spesa/ROAS/vendite/click usa execute_sql su fact_campaign_daily. Espone anche bidding_strategy e placement_adjustments = moltiplicatori % ATTUALI per placement (PLACEMENT_TOP | PLACEMENT_REST_OF_SEARCH | PLACEMENT_PRODUCT_PAGE | SITE_AMAZON_BUSINESS): per la PERFORMANCE per placement (spesa/ACoS/vendite Top of Search vs Product Pages vs Rest of Search) usa execute_sql su fact_campaign_placement_daily. audience_adjustments = moltiplicatori % ATTUALI per SEGMENTO DI PUBBLICO [{audience_id, percentage}] (nomi con ads_list_sp_audiences, modifica con ads_update_sp_audience_bidding).

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_sp_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_filterNoREAD-ONLY: ID specifici delle campagne SP da cercare

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / campaign_id_filter
      Added value: +{
      +  "description": "READ-ONLY: ID specifici delle campagne SP da cercare",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 100,
      +  "minItems": 1,
      +  "type": "array"
      +}
  2. Changed2 schema fields changed
    • 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."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses that results reflect current live state, that there is no campaign-level bid, that daily_budget is numeric in marketplace currency, and that placement_adjustments/audience_adjustments are CURRENT percentage multipliers rather than performance data. It also clarifies what the tool does not return, which prevents misuse for reporting.

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?

The purpose and the LIVE qualifier are front-loaded, followed by field semantics and routing guidance; nearly every sentence carries actionable information. It is dense and long, with several parenthetical enumerations that could be trimmed, but nothing is redundant filler.

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?

There is no output schema, and the description compensates by explaining the returned field set, the meaning of the multiplier fields and their enum-like values, and the absence of performance metrics. For a read-only list tool with fully documented parameters, an agent has everything needed to call it correctly and interpret results.

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 four parameters (account_id, profile_id, state_filter, campaign_id_filter) are already documented in the schema. The description adds semantics about returned fields (targetingType values, currency of daily_budget) but says nothing extra about the filter parameters, 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?

The description states a specific verb+resource: reading the LIVE/current state of SP campaigns, and enumerates key fields returned (name, campaignId, state, targetingType, daily_budget). It explicitly distinguishes itself from performance-related siblings by naming execute_sql over fact_campaign_daily and fact_campaign_placement_daily, so an agent can tell it apart from ads_list_sb_campaigns/ads_list_sd_campaigns and from SQL analysis without opening a schema.

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?

It gives explicit positive use cases ("Usa per VERIFICARE prima di agire o per avere nomi/ID") and explicit exclusions ("NON ritorna performance: per ACoS/spesa/ROAS/vendite/click usa execute_sql su fact_campaign_daily"), plus a second routing rule for placement performance. It also routes audience-name resolution to ads_list_sp_audiences.

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