tool4seller-mcp

Prepare product changes

prepare_product_changes

Prepares and saves a confirmable plan to change product prices, titles, item highlights, generic keywords, bullet points, or descriptions. Does not submit changes to Amazon.

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": {
      "parameters": "<parameters>"
    },
    "name": "prepare_product_changes"
  }
}

Input Schema

Name	Required	Description	Default
`parameters`	Yes

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?

Beyond the annotations, it discloses the central behavior: a plan is saved while no remote Amazon change occurs. This is consistent with the non-read-only, non-destructive, closed-world hints, but validation behavior, plan lifetime, and how confirmation leads to application are not explained.

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?

Two sentences front-load the operation, editable scope, and crucial no-submission caveat. There is no redundant or speculative wording.

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?

Together with the detailed nested schema and output schema, the description supplies enough information to understand the tool's role and avoid treating it as a live Amazon update. The main remaining gap is workflow routing—what to use to inspect, confirm, or apply the saved plan—rather than missing return-value documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The six-field list mirrors the nested schema and confirms scope, but adds no formats, omission/replacement semantics, or batching guidance. It does not explain the undocumented top-level `parameters` object or its required `storeId` and `items`; with reported schema coverage of 0%, the description only partly compensates, even though the nested schema itself is detailed.

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?

The description uses a specific verb and resource: it prepares and saves a confirmable plan for six named kinds of product-listing changes. The explicit statement that it does not submit changes to Amazon also distinguishes it from the sibling `apply_product_changes`.

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 confirmable-plan wording and non-submission caveat clearly establish this as the staging step for a product update rather than the execution step. It would be stronger with an explicit route to `apply_product_changes` or `confirm_workflow_plan` and any prerequisites, so the guidance is clear but not complete.

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?