tool4seller-mcp

Apply ad group creation

apply_ad_group_creation

Destructive

Executes only a confirmed AD_AD_GROUP_CREATE plan on the authorized Amazon Ads account. Creates advertising ad 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

Behavior4/5

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

Annotations already declare destructive/openWorld writes; the description adds genuine context beyond them — real writes to the authorized account, one-time receipt semantics, idempotency, and that a linked draft may auto-prepare a next preview without confirming or executing it. Sandbox simulation behavior is disclosed rather than left to inference.

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?

Four front-loaded sentences with no filler: action and scope first, then prerequisites, then continuation behavior, then sandbox caveat. Dense but every clause carries operational meaning.

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?

Return values are covered by the output schema, and the description handles the hard parts: continuation eligibility, automatic next-preview preparation, and sandbox divergence. Combined with the schema's retry/reconciliation notes, an agent has what it needs to call this safely.

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% and the parameter descriptions are far richer than the tool description (timeouts, INDETERMINATE reconciliation, key reuse rules). The description only restates that a confirmation receipt and idempotency key are required, adding little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Executes ... Creates advertising ad groups') scoped to AD_AD_GROUP_CREATE plans on the authorized Amazon Ads account. The plan-type scoping implicitly separates it from prepare_ad_group_creation and apply_ad_group_changes, though neither sibling is named.

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?

Makes the prerequisite chain explicit: only a confirmed plan, requiring the one-time confirmation receipt and an idempotency key, so an agent knows it must come after confirm_workflow_plan. It also distinguishes the Review Sandbox case, but never states when to use apply_ad_group_changes instead.

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?