Skip to main content
Glama

ads_create_sp_ad_group

Create a SP ad group in an existing campaign. Defaults to PAUSED so it can be populated before delivery. IMPORTANTE — un ad group è O keyword-targeted O product-targeted, MAI entrambi: Amazon RIFIUTA (otherError) una keyword in un ad group che ha già product target, e viceversa. Quindi se ti servono SIA keyword SIA target di prodotto, crea DUE ad group separati nella stessa campagna: uno popolato con ads_create_sp_keywords, l'altro con ads_create_sp_product_targets. Le NEGATIVE keyword/target invece convivono con qualsiasi tipo.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ad_group": "<ad_group>"
    },
    "name": "ads_create_sp_ad_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_groupYesAd group da creare: oggetto { campaignId, name, defaultBid, state } (formato Amazon Ads v3).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
confirm_idNoToken di conferma ritornato dall'anteprima. Ripassa lo STESSO payload + confirm_id per eseguire davvero la scrittura.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / ad_group / description
      Added value: +"Ad group da creare: oggetto { campaignId, name, defaultBid, state } (formato Amazon Ads v3)."
    • addedInput schema / properties / ad_group / properties / campaign_id / description
      Added value: +"Id campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns)."
    • addedInput schema / properties / ad_group / properties / default_bid / description
      Added value: +"Bid predefinito dell'ad group in valuta del marketplace, es. 0.45."
    • addedInput schema / properties / ad_group / properties / name / description
      Added value: +"Nome della campagna/portfolio/ad group, visibile in console Amazon Ads."
    • addedInput schema / properties / ad_group / properties / profile_id / description
      Added value: +"Amazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost."
    • addedInput schema / properties / ad_group / properties / state / description
      Added value: +"Stato: ENABLED, PAUSED oppure ARCHIVED (maiuscolo; ARCHIVED è irreversibile)."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond them — the default PAUSED state so the ad group can be populated before delivery, and the concrete API failure mode (otherError) that results from mixing target types. It stops short of describing the confirm_id preview/execute handshake or duplicate-name behavior, leaving those to the schema.

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

Conciseness3/5

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

The purpose and the PAUSED default are front-loaded correctly, but the second half is a long mixed-language block (English/Italian) with heavy capitalization that reads as a warning banner rather than a spec. The content is worth keeping; the delivery is more verbose and harder to parse than necessary.

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 nested-object creation tool with no output schema and full schema coverage, the description covers the essential behavioral facts an agent needs before calling. It omits the confirm_id two-step confirmation flow, but that is documented in the input schema itself, so the gap is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description still earns a bump by disclosing that state defaults to PAUSED, which the schema enum does not state, and by constraining what the created ad group should later be populated with.

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 ('Create a SP ad group in an existing campaign') and immediately names the two sibling tools used to populate it (ads_create_sp_keywords, ads_create_sp_product_targets), so an agent can place it in the workflow 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?

Gives explicit routing rules: an ad group is either keyword-targeted or product-targeted, and if both are needed the agent must create two separate ad groups in the same campaign. It also carves out the negative-keyword case as exempt, which is exactly the when/when-not detail that prevents a failed call.

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