Skip to main content
Glama

ads_list_sb_keywords

Read-only

LIVE: keyword Sponsored Brands (SB) con BID e stato ATTUALI — la lettura da fare prima di riofferire su SB. Filtra con campaign_id/ad_group_id. NON ritorna performance: per spesa/vendite/ACoS usa execute_sql su fact_keyword_daily. Elenco vuoto = quel brand non ha keyword SB (tipico se le campagne SB usano product targeting o non esistono): dillo, NON inventare keyword.

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

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.
ad_group_idNoId ad group Amazon Ads (stringa numerica, da ads_list_*_ad_groups).
campaign_idNoId campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns).
state_filterNoFiltra per stato: array con ENABLED, PAUSED, ARCHIVED.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / ad_group_id / description
      Added value: +"Id ad group Amazon Ads (stringa numerica, da ads_list_*_ad_groups)."
    • addedInput schema / properties / campaign_id / description
      Added value: +"Id campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns)."
    • 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.3/5.0
Behavior4/5

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

Annotations already declare read-only and closed-world behavior, but the description adds genuinely new context: the data is live/current rather than historical, performance metrics are deliberately excluded, and an empty list has a specific meaning (no SB keywords, common when campaigns use product targeting). Pagination or result-size behavior is not covered, which keeps it below 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-data scope, then filtering, then the exclusion and the empty-result warning — a sensible priority order. Slightly dense with caps and multiple clauses, but every sentence carries information.

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?

Five optional parameters, no output schema, and the description covers the two things an agent most needs: what fields come back (current bid and state) and what does not (performance). It stops short of describing result ordering or volume, which would matter for a large keyword list.

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 coverage is 100%, so every parameter is already documented, including state_filter's enum values. The description only echoes campaign_id/ad_group_id as filters and says nothing about state_filter or account_id/profile_id precedence. Baseline 3 is appropriate.

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 ('keyword Sponsored Brands (SB) con BID e stato ATTUALI') and implicitly separates itself from the SP equivalent by naming the SB scope explicitly. An agent knows exactly what list it gets back: SB keywords with current bid and state.

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 names the moment to use it ('la lettura da fare prima di riofferire su SB') and routes performance questions to a different tool ('per spesa/vendite/ACoS usa execute_sql su fact_keyword_daily'). It also tells the agent how to interpret an empty result instead of fabricating keywords.

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