Skip to main content
Glama

ads_create_sp_product_targets

Destructive

Create SP targets. MANUAL (campagne MANUAL): ogni target { campaign_id, ad_group_id, bid, e uno tra: asin (ASIN target), category_id (category target), expression (raw v3) }. AUTO (campagne AUTO): per impostare il bid sui 4 gruppi di matching automatico usa { campaign_id, ad_group_id, bid, auto_match: "close"|"loose"|"substitutes"|"complements" } (close=ricerche strettamente correlate, loose=genericamente correlate, substitutes=prodotti alternativi, complements=accessori). ATTENZIONE: su una campagna AUTO GIÀ ESISTENTE i 4 gruppi sono già stati creati da Amazon — ri-crearli qui dà errore INVALID_ARGUMENT. Per cambiarne solo il bid NON usare questo tool: usa ads_list_sp_targets per leggere il targetId del gruppo e poi ads_update_sp_target_bid.

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": {
      "targets": "<targets>"
    },
    "name": "ads_create_sp_product_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetsYesTarget da creare: array di oggetti (campi nella descrizione del tool).
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. Changed1 schema field changed
    • addedInput schema / properties / targets / description
      Added value: +"Target da creare: array di oggetti (campi nella descrizione del tool)."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds real behavioral value beyond that: the INVALID_ARGUMENT failure on pre-existing AUTO campaigns and the meaning of each auto_match value. It does not mention the preview/confirm two-step write flow in the prose, though the schema's confirm_id field covers that.

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?

Content is front-loaded: one-line purpose, then MANUAL, AUTO, and a warning block, so an agent can scan to the relevant mode quickly. Every sentence carries information, but the dense parenthetical payload notation mixed with an English/Italian switch makes it slightly harder to parse than it needs to be.

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 destructive write tool with two payload variants and no output schema, the description covers the shapes, the match-type semantics, and the main error condition. The remaining gap is that the confirmation-token workflow lives only in the schema's confirm_id description rather than being surfaced in the tool prose.

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

Parameters5/5

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

Although schema coverage is nominally 100%, the targets array is a nested object whose fields are explicitly delegated to the description ("campi nella descrizione del tool"). The description supplies those fields, the mutual-exclusivity rule (one of asin/category_id/expression), and the full auto_match enum with semantic glosses (close=strictly related searches, loose=generally related, substitutes/complements) — meaning available nowhere else in the structured data.

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 opens with a specific verb and resource ("Create SP targets") and then splits the operation into its two concrete modes, MANUAL and AUTO, each with its exact payload shape. It also names the sibling tools it is not (ads_update_sp_target_bid, ads_list_sp_targets), so an agent can distinguish it without opening another 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?

It states both when to use the tool (creating MANUAL targets by asin/category_id/expression, or setting bids on AUTO match groups) and an explicit when-not-to-use with the correct alternative: to change only the bid, use ads_list_sp_targets to get the targetId and then ads_update_sp_target_bid. The negative case is tied to a concrete failure mode (recreating existing AUTO groups yields INVALID_ARGUMENT).

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