Skip to main content
Glama

ads_list_sd_ad_groups

Read-only

Read-only: ad group Sponsored Display — id, nome, stato, campagna di appartenenza e defaultBid (l'offerta dell'ad group, la leva di ottimizzazione SD). 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_sd_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.
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

A3.7/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 leading 'Read-only' partly repeats structured data. The valuable addition is the field inventory of the returned objects — with no output schema present, telling the agent it gets back id, name, state, campaign and defaultBid is the main behavioral disclosure, though pagination or result-count limits remain unstated.

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?

A single compact sentence is front-loaded with the read-only nature and the resource, and the parenthetical gloss on defaultBid as the SD optimization lever earns its place. Slight density from mixing a field list and a filter instruction in one sentence, but nothing is wasted.

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 simple four-parameter, all-optional list tool with full schema coverage, the description covers the main gap left by the absent output schema by enumerating returned fields. Missing are any indication of result volume, pagination, or ordering, which an agent would need for large accounts.

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 all four parameters (account_id, profile_id, state_filter, campaign_id_filter) are already documented in the schema. The description only echoes campaign_id_filter and adds the parenthetical meaning of defaultBid, which is a return field rather than a parameter, so it adds little parameter meaning beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource (Sponsored Display ad groups) and enumerates the returned fields (id, name, state, owning campaign, defaultBid), which is far more specific than a bare list op. It implicitly separates itself from ads_list_sb_ad_groups and ads_list_sp_ad_groups by naming the Sponsored Display product, though it never names those siblings explicitly.

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?

The closing phrase 'Filtra con campaign_id_filter' gives one concrete usage hint for narrowing results, which is real guidance. However there is no statement of when to prefer this over ads_list_sd_campaigns or how it relates to ads_update_sd_ad_group, and no exclusions or prerequisites are given.

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