Skip to main content
Glama

ads_list_sb_ad_groups

Read-only

Read-only: elenco ad group Sponsored Brands (SB) — id, nome, stato (ENABLED|PAUSED|ARCHIVED), campagna di appartenenza. Filtra con campaign_id_filter.

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

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.
campaign_id_filterNoLimita ai soli id campagna indicati (array di stringhe numeriche).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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."
  2. First observed

TDQS

A4/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, so the safety profile is covered and the description's "Read-only" is largely redundant. The description does add value beyond annotations by enumerating the returned fields and the state enum (ENABLED|PAUSED|ARCHIVED) in the absence of an output schema, though it says nothing about pagination or result limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single compact sentence with the operation class front-loaded ("Read-only"), followed by the resource, the returned fields, and the filter hint. Nothing is wasteful and no meaning is buried.

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 three-optional-parameter list tool with full schema coverage and no output schema, the definition supplies nearly everything an agent needs: scope, returned fields, and the filter mechanism. The only gap is absence of any statement about result volume or pagination behavior.

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 and campaign_id_filter thoroughly. The description only restates that campaign_id_filter narrows the result, adding no syntax or edge-case detail (e.g. empty array behavior). 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 names a specific verb ("elenco") and resource ("ad group Sponsored Brands (SB)") and even lists the returned fields: id, nome, stato, campagna di appartenenza. The explicit "SB" qualifier distinguishes it from the sibling ads_list_sd_ad_groups and ads_list_sp_ad_groups without needing to open any schema.

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

Usage Guidelines3/5

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

"Filtra con campaign_id_filter" gives one actionable usage pointer, and "Read-only" signals the operation class. However, there is no explicit when-not-to-use guidance, no mention of the ads_update_sb_ad_group alternative for mutations, and no statement about default scope when no filter is supplied.

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