Sellantica Amazon Ads

Prepare one or more product target create previews

prepare_product_target_create_v1

DestructiveIdempotent

Create an idempotent, auditable write intent to create one or more brand-new ASIN (product) targets in existing ad groups. adgroup_id must come from get_ad_groups; the target ASIN must not already be targeted in that ad group. Nothing changes on Amazon or in Sellantica until the returned request is confirmed via approve_write_v1 and then execute_write_v1. The preview states will_dispatch: true means execute_write_v1 sends it to Amazon, false (execution_mode PREVIEW_ONLY) means it is recorded and never sent. To edit an existing target's bid or state (including an existing product target) instead of creating one, use prepare_target_bid_v1; to create a product AD (the ad itself, not a targeting clause) use prepare_product_ad_create_v1 instead.

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": {
      "profile_id": "<profile_id>",
      "profile_pk": "<profile_pk>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "prepare_product_target_create_v1"
  }
}

Input Schema

Name	Required	Description
`bid`	No	Bid in the marketplace's currency for the new product target, greater than 0 and at most 100.
`asin`	No	Target ASIN (B-prefixed, e.g. B0CXYZ1234) or 10-digit ISBN to target, unique per ad group.
`items`	No	Batch form: an array of per-target create objects (adgroup_id, asin, bid, state?). Use this instead of the flat arguments to create more than one product target in a single call; never pass both.
`state`	No	Initial target state: ENABLED or PAUSED. Defaults to ENABLED.
`adgroup_id`	No	Amazon ad group id the new product target is created in, from get_ad_groups. Use this or items, not both.
`profile_id`	Yes	Amazon Ads profile id, from list_profiles.
`profile_pk`	Yes	Sellantica's internal profile primary key, from list_profiles (needed when profile_id is not unique).
`idempotency_key`	Yes	Caller-chosen key (6-128 safe characters) that makes a retry of this exact call return the same write request instead of creating a duplicate.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare the mutation profile, but the description adds important workflow context: nothing changes until `approve_write_v1` and `execute_write_v1`, and `will_dispatch` distinguishes real dispatch from PREVIEW_ONLY recording. It also explains the idempotency contract, which is more than the annotations alone convey.

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?

The definition is dense and front-loaded: it starts with the exact operation, then gives prerequisites, approval behavior, dispatch semantics, and sibling alternatives. Each sentence carries necessary routing or behavioral information without filler.

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

Completeness5/5

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

For a complex mutation tool with no output schema, the description supplies the critical return-semantic context via `will_dispatch`, explains the approval/execution lifecycle, and routes to alternatives. Nothing essential for correct invocation appears missing.

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 parameters such as bid, ASIN, state, and mutual exclusivity of flat arguments versus `items`. The description reinforces constraints like `adgroup_id` source and ASIN uniqueness, but does not add substantial meaning beyond the schema.

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: creating an auditable write intent for brand-new ASIN product targets in existing ad groups. It also names the sibling alternatives `prepare_target_bid_v1` and `prepare_product_ad_create_v1`, clearly distinguishing this tool from related prepare operations.

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?

Explicitly covers when to use this tool versus alternatives: edit existing targets via `prepare_target_bid_v1`, create the product ad itself via `prepare_product_ad_create_v1`. It also states prerequisites (`adgroup_id` from `get_ad_groups`, ASIN not already targeted) and the required approval/execution chain.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sellantica Amazon Ads tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?