tool4seller-mcp

Apply targeting creation

apply_targeting_creation

Destructive

Executes only a confirmed AD_TARGETING_CREATE plan on the authorized Amazon Ads account. Creates positive keyword, positive ASIN, negative keyword, or negative ASIN targeting entities. A batch may contain multiple targeting groups. Requires the plan's one-time confirmation receipt and an idempotency key. A linked structure draft may automatically prepare the next preview without confirming or executing it. Review Sandbox simulates advertising writes and skips continuation.

Input Schema

Name	Required	Description
`planId`	Yes	Confirmed immutable workflow plan ID. If this call times out or disconnects, do not prepare a replacement plan: query get_workflow_plan, or retry this exact plan with the same idempotency key. An INDETERMINATE item means Amazon may have accepted the write and must be reconciled before any retry.
`idempotencyKey`	Yes	Client-generated key unique to this plan. Generate a new key for every newly prepared plan; include the planId or another random value. Reuse the exact key only when retrying apply for this same plan; never reuse it for a newly prepared plan.
`applyContinuation`	No	For atomic plans belonging to an AD_STRUCTURE_CREATE draft. Pass the applyContinuation object returned by continue_workflow_draft or the previous apply result unchanged with its current plan. After the approved write finishes, the server prepares the next-stage preview without confirming or executing it. If omitted, continuation may still be recovered from the active linked plan. Review Sandbox skips automatic continuation.
`confirmationReceipt`	Yes	One-time receipt returned by confirm_workflow_plan for this exact plan. A receipt for the current plan does not confirm subsequent plans.

Output Schema

Name	Required	Description	Default
`items`	No
`planId`	No
`status`	No
`storeId`	No
`summary`	No
`planHash`	No
`policyId`	No
`warnings`	No
`createdAt`	No
`expiresAt`	No
`simulated`	No
`parameters`	No
`confirmedAt`	No
`nextActions`	No
`planVersion`	No
`continuation`	No
`workflowType`	No
`executionMode`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare non-read-only, destructive, and open-world. The description adds real value beyond them by disclosing batch semantics, the automatic next-stage preview preparation, and sandbox write simulation that skips continuation. It does not address partial-failure or reconciliation behavior in the description proper (that lives only in the planId schema text).

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?

Front-loaded with the core operation and only six sentences, each carrying a distinct constraint (scope, entity types, batch, receipt/key, continuation, sandbox). One or two clauses are dense but nothing is filler.

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?

With an output schema present and fully documented parameters, the description only needs to cover invocation preconditions and side effects, which it does: confirmation requirement, idempotency, continuation behavior, and sandbox divergence. The remaining gap is guidance on reconciling INDETERMINATE outcomes, which is delegated to the schema text.

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 carries the semantics for planId, idempotencyKey, confirmationReceipt, and applyContinuation. The description only mentions that a receipt and idempotency key are required, adding no syntax or format detail. Baseline 3 applies.

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: executes a confirmed AD_TARGETING_CREATE plan and enumerates the entity types it creates (positive/negative keyword and ASIN targeting). The plan-type qualifier distinguishes it cleanly from apply_targeting_changes and from the prepare_* siblings.

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

Usage Guidelines4/5

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

Explicitly restricts use to plans that are already confirmed, and names the required receipt and idempotency key. It also flags the sandbox variant and the continuation side-effect. It does not explicitly route the agent to confirm_workflow_plan or prepare_targeting_creation as the preceding steps, which keeps it from a 5.

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

All tool4seller-mcp 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?