tool4seller-mcp

Apply portfolio creation

apply_portfolio_creation

Destructive

Executes only a confirmed AD_PORTFOLIO_CREATE plan on the authorized Amazon Ads account. Creates advertising portfolios with optional budgets. Requires the plan's one-time confirmation receipt and an idempotency key. Review Sandbox simulates advertising writes.

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": {
      "planId": "<planId>",
      "confirmationReceipt": "<confirmationReceipt>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "apply_portfolio_creation"
  }
}

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.
`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.

AddedNov 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructive=true, readOnlyHint=false and openWorldHint=true, so the safety bar is partly covered; the description still adds meaningful context about the confirmation receipt being one-time and bound to this exact plan. The retry/INDETERMINATE reconciliation guidance largely duplicates the schema property text rather than extending it.

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 covering capability, preconditions, safety, and the sandbox alternative, with no filler. Minor redundancy between "Executes only a confirmed AD_PORTFOLIO_CREATE plan" and "Creates advertising portfolios" but nothing wasted.

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?

An output schema exists, so return values need not be described, and the annotations cover the destructive/open-world profile. The description supplies prerequisites and failure-mode routing, leaving only the prepare/confirm sibling handoff implicit.

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% and each parameter already carries detailed prose, so the description's mention of the receipt and idempotency key repeats structured data. Baseline 3 applies since the schema does the heavy lifting and the description adds no new parameter meaning.

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_PORTFOLIO_CREATE plan", "Creates advertising portfolios with optional budgets") and constrains scope to a confirmed plan, which cleanly separates it from prepare_portfolio_creation and apply_portfolio_changes. An agent can identify the tool without opening the schema.

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 precondition explicit (only a confirmed plan, requires the one-time confirmation receipt and an idempotency key) and points at Review Sandbox for simulation instead of live writes. It stops short of naming prepare_portfolio_creation or confirm_workflow_plan directly, so the prepare→confirm→apply chain must be inferred from the receipt language.

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?