Skip to main content
Glama

ForthClear Liquidation Marketplace

Bulk update listing prices or MOQ

bulk_update_listings
Destructive

Change the price or the minimum order quantity on up to 200 of your listings. Requires sign-in with seller access. price_set takes price_cents (integer cents). value_usd is an explicit dollar amount and is deprecated. The percent modes adjust the current price, and moq_set writes a minimum order quantity. Previous values are replaced. 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>",
      "mode": "<mode>"
    },
    "name": "bulk_update_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesWhat to change and how: price_set writes an absolute unit price in cents via price_cents, price_percent_increase / price_percent_decrease adjust the current price by a percentage, moq_set writes a minimum order quantity.
valueNoPercent (0-1000) for percent modes, or integer units (1-999999) for moq_set. Not accepted for price_set.
value_usdNoDeprecated. For price_set only, an explicit price in US dollars. Prefer price_cents.
price_centsNoFor price_set only. Absolute unit price in cents. 5000 means $50.00.
product_idsYesForthClear product ids to update (max 200/request).

Output Schema

NameRequiredDescriptionDefault
modeYes
messageYes
successYes
updatesYes
updated_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"What to change and how: price_set writes an absolute USD price, price_percent_increase / price_percent_decrease adjust the current price by a percentage, moq_set writes a minimum order quantity."New value: +"What to change and how: price_set writes an absolute unit price in cents via price_cents, price_percent_increase / price_percent_decrease adjust the current price by a percentage, moq_set writes a minimum order quantity."
    • addedInput schema / properties / price_cents
      Added value: +{
      +  "description": "For price_set only. Absolute unit price in cents. 5000 means $50.00.",
      +  "type": "integer"
      +}
    • changedInput schema / properties / value / description
      Previous value: -"USD price for price_set, percent (0-1000) for percent modes, integer units (1-999999) for moq_set."New value: +"Percent (0-1000) for percent modes, or integer units (1-999999) for moq_set. Not accepted for price_set."
    • addedInput schema / properties / value_usd
      Added value: +{
      +  "description": "Deprecated. For price_set only, an explicit price in US dollars. Prefer price_cents.",
      +  "type": "number"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "product_ids",
      -  "mode",
      -  "value"
      -]New value: +[
      +  "product_ids",
      +  "mode"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "message": {
      +      "type": "string"
      +    },
      +    "mode": {
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    },
      +    "updated_count": {
      +      "type": "integer"
      +    },
      +    "updates": {
      +      "items": {
      +        "properties": {
      +          "after": {
      +            "type": "number"
      +          },
      +          "before": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "before",
      +          "after"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "mode",
      +    "updated_count",
      +    "updates",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / mode / description
      Added value: +"What to change and how: price_set writes an absolute USD price, price_percent_increase / price_percent_decrease adjust the current price by a percentage, moq_set writes a minimum order quantity."
  3. First observed

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 that previous values are replaced (concrete destructive semantics), that auth needs the seller:write scope, that a user approval prompt fires every time, and the batch cap. It still omits atomicity/partial-failure behavior for a 200-item mutation and any rate-limit detail, which matters for a non-idempotent destructive bulk write.

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?

The action and its scope are front-loaded, then each following sentence covers one concern (auth, mode semantics, deprecation, replacement behavior, scope/approval) with no filler. The telegraphic fragments are dense rather than padded.

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?

With an output schema present, return values need no explanation, and the description covers auth, batch limits, mode semantics, and deprecation well. The remaining gap is what happens when some of the 200 ids fail or are invalid, which is material for a bulk destructive operation.

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 already 100%, so the baseline is 3; the description earns above that by explaining mode interactions (price_set uses price_cents, percent modes adjust the current price, moq_set writes a quantity) and by flagging value_usd as deprecated. It adds interpretation rather than restating field descriptions.

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?

The opening sentence gives a specific verb (change), the exact fields affected (price or minimum order quantity), and the batch scope (up to 200 of your listings). That makes it clearly distinguishable from create_listing or set_listing_shipping on the surface, though no sibling is named explicitly.

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?

It establishes real prerequisites: seller sign-in, the seller:write scope, the 200-listing ceiling, and per-call user approval. It also routes away from the deprecated value_usd toward price_cents, but never states when to prefer this tool over creating a new listing or other listing tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources