Skip to main content
Glama

ads_list_sp_ad_groups

Read-only

Read-only list of Sponsored Products ad groups (id, name, state, default bid)

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_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_idNoId campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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."
  2. First observed

TDQS

B3.2/5.0
Behavior3/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 'Read-only' in the description adds nothing beyond structured data. What does add value is the parenthetical listing the returned fields (id, name, state, default bid), which is real behavioral disclosure given there is no output schema. Pagination, result limits and empty-result behavior are still undisclosed.

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 efficient line with the key qualification ('Sponsored Products') front-loaded and the return fields appended compactly. Nothing is wasted, though it is arguably under-written rather than well-structured prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity read tool with full schema coverage and read-only annotations, the definition is barely sufficient: it covers what is returned but not how results are scoped or whether empty lists are possible. No output schema exists, so the field list is doing important work, but it is not exhaustive.

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% — account_id, profile_id and campaign_id are all documented in the schema, including fallback behavior when omitted. The description adds no extra meaning about how these parameters filter the result set, so the baseline of 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 a specific verb (list) and resource (Sponsored Products ad groups), so an agent can distinguish it from ads_list_sb_ad_groups and ads_list_sd_ad_groups by the ad product alone. It also names the fields returned. It stops short of a full sibling comparison, but the ad-product qualifier does the essential disambiguation.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance, and no statement about whether the call is scoped by account/profile/campaign or returns everything. The agent must infer usage from the name and from the optional parameters in the schema.

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