ForthClear Liquidation Marketplace

Set listing shipping

set_listing_shipping

DestructiveIdempotent

Set how your listings ship: the shipping price per unit, or that shipping is quoted per order, and the lot type (parcel, pallet, truckload or mixed). Optionally set where your stock ships from; that is part of your seller account and shows on all your listings. Requires sign-in with seller access. Up to 200 of your listings per call; every id must be yours or nothing changes. shipping_price_cents is charged per unit at checkout (0 means free shipping). quote_shipping=true removes the fixed price so buyers ask for a quote, and turns off instant checkout on those listings, because instant checkout needs a fixed shipping price. OAuth discovery: /.well-known/oauth-authorization-server (scope seller:write). Sensitive: requires user approval each time.

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": {
      "product_ids": "<product_ids>"
    },
    "name": "set_listing_shipping"
  }
}

Input Schema

Name	Required	Description
`lot_type`	No	How the lot ships: parcel (boxes by courier), pallet, truckload, or mixed.
`product_ids`	Yes	Your ForthClear product ids (max 200 per call).
`quote_shipping`	No	true: no fixed shipping price; buyers request a quote that includes shipping. Turns off instant checkout on these listings. Not with shipping_price_cents.
`ship_from_region`	No	Optional state or region your stock ships from, for example Michigan. Applies to your whole seller account. Only with ship_from_country.
`ship_from_country`	No	Two-letter country code your stock ships from, for example US. Applies to your whole seller account.
`shipping_price_cents`	No	Shipping price per unit in cents, charged per unit at checkout. 0 means free shipping. Not with quote_shipping.

Output Schema

Name	Required	Description	Default
`message`	Yes
`success`	Yes
`updates`	Yes
`ship_from`	Yes
`updated_count`	Yes
`instant_checkout_turned_off`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, and the description adds real context beyond them: the all-or-nothing write ('every id must be yours or nothing changes'), the account-wide side effect of ship_from fields affecting every listing, the loss of instant checkout when quote_shipping is true, and the per-call user approval requirement. That is exactly the behavior an agent needs before mutating data.

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?

Dense but front-loaded: the core action and its options come first, constraints and side effects follow. The trailing OAuth discovery URL and 'Sensitive: requires user approval each time' sentence are meta-detail about transport rather than tool behavior, which slightly dilutes the core message.

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?

For a destructive, open-world, six-parameter mutation with an output schema, the description covers auth, limits, atomicity, cross-listing side effects, parameter interactions, and approval requirements. Nothing an agent needs to call it safely is missing, and return values are covered by the output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds economic meaning the schema does not: shipping_price_cents is charged per unit at checkout and 0 means free, quote_shipping suppresses the fixed price and disables instant checkout, and ship_from values are account-level rather than listing-level. That is meaningful beyond the field descriptions.

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?

Opens with a specific verb and resource plus the exact fields being set (price per unit, quote-per-order, lot type, ship-from), which lets an agent distinguish it from bulk_update_listings and create_listing without opening a schema. The scope ('your listings') is stated up front.

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?

Gives clear preconditions for use: seller sign-in required, max 200 listings per call, all ids must be owned by the caller, and the quote_shipping vs shipping_price_cents mutual exclusion is spelled out. It stops short of naming a sibling tool to use instead for other listing edits, so no explicit alternative routing.

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

All ForthClear Liquidation Marketplace 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?