tool4seller-mcp

Apply targeting changes

apply_targeting_changes

Destructive

Executes only a confirmed AD_TARGETING_CHANGE plan on the authorized Amazon Ads account. Changes positive keyword or ASIN targeting bids or states, or re-enables/archives negative keyword or ASIN targeting. Negative targeting has no bid actions; archiving is irreversible. 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

TableJSON 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

TableJSON 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

A4.4/5.0

Behavior5/5

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

Annotations already declare destructive=true and openWorld=true, and the description adds substantial context beyond that: 'archiving is irreversible,' negative targeting has no bid actions, a one-time confirmation receipt and idempotency key are required, and sandbox mode skips continuation. These are exactly the operational traits an agent needs before invoking a destructive write.

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?

The preconditions and irreversibility warning are front-loaded, but the run-on sentence about continuation and the schema-level prose about nextActions/presenting previews add density that could be tightened. Still, every clause carries operational meaning.

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?

With an output schema present, return values needn't be explained; the description still covers the critical edge cases (irreversible archive, idempotency/retry posture, continuation behavior, sandbox simulation), leaving nothing an agent needs to call it correctly.

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 coverage is 100%, so the schema already documents planId, idempotencyKey, confirmationReceipt, and the applyContinuation nested object in detail. The description only restates that a receipt and idempotency key are required, adding no syntax or semantics beyond the schema, so 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 ('executes') on a specific resource ('confirmed AD_TARGETING_CHANGE plan') and enumerates the exact operations covered (positive bid/state changes, re-enable/archive negative targeting). This clearly differentiates it from siblings like prepare_targeting_changes and apply_targeting_creation.

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?

The description establishes the precondition (only a confirmed plan) and explains downstream behavior (auto-prepared next-stage preview, sandbox skipping continuation), which tells the agent when this tool applies. It doesn't explicitly name alternatives for the non-confirmed case, but the gating condition is unambiguous.

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?