ForthClear Liquidation Marketplace

Create a listing

create_listing

Create a new product listing (seller tool)

Input Schema

TableJSON Schema

Name	Required	Description
`sku`	No	Seller's own stock-keeping unit, shown to buyers and used for reconciliation.
`name`	Yes	Listing title shown to buyers and matched by catalogue search.
`category`	Yes	Catalogue category. One of: electronics, apparel, home_goods, beauty, sports, kitchenware, office_supplies, toys, food_beverage, tools, other.
`quantity`	Yes	Units available in this lot.
`condition`	Yes	Standard liquidation condition grade (Task #72)
`description`	No	Listing body copy: condition detail, packaging, lot composition. Buyers filter on its presence and agents summarise it.
`price_per_unit`	Yes	Price in cents
`original_retail_price`	No	Original retail price in cents

Output Schema

TableJSON Schema

Name	Required	Description	Default
`listing`	Yes
`message`	Yes
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "listing": {
+      "properties": {
+        "category": {
+          "type": "string"
+        },
+        "condition": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "type": "string"
+        },
+        "image_url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "type": "string"
+        },
+        "original_retail": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "price": {
+          "description": "Unit price in cents.",
+          "type": "integer"
+        },
+        "quantity": {
+          "type": "integer"
+        },
+        "sku": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "type": "string"
+        },
+        "view_url": {
+          "description": "Buyer-facing listing page.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name",
+        "category",
+        "quantity",
+        "price",
+        "status",
+        "view_url"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "message",
+    "listing"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedAug 29, 2026

addedInput schema / properties / category / description

Added value: +"Catalogue category. One of: electronics, apparel, home_goods, beauty, sports, kitchenware, office_supplies, toys, food_beverage, tools, other."

addedInput schema / properties / category / enum

Added value: +[
+  "electronics",
+  "apparel",
+  "home_goods",
+  "beauty",
+  "sports",
+  "kitchenware",
+  "office_supplies",
+  "toys",
+  "food_beverage",
+  "tools",
+  "other"
+]

addedInput schema / properties / description / description

Added value: +"Listing body copy: condition detail, packaging, lot composition. Buyers filter on its presence and agents summarise it."

addedInput schema / properties / name / description

Added value: +"Listing title shown to buyers and matched by catalogue search."

addedInput schema / properties / quantity / description
```
Added value: +"Units available in this lot."
```

addedInput schema / properties / sku / description

Added value: +"Seller's own stock-keeping unit, shown to buyers and used for reconciliation."

First observedAug 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing behavioral beyond that: it does not say whether the listing publishes immediately, requires moderation, or is reversible. With the annotation bar in place, this near-zero added context warrants a 2.

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?

A single front-loaded sentence with zero filler, so nothing is wasted. The size is arguably too lean for an 8-parameter creation tool, but as a conciseness measure it is tight and well-formed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 8 parameters, 5 required, and mutating side effects in an open-world marketplace, yet the description omits what happens on success (e.g., listing visibility, review flow). The output schema covers return values and the schema covers inputs, but the operational context an agent needs before invoking a non-idempotent create is absent.

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%, including enum documentation for category and condition and unit notes for prices in cents, so the schema carries the full burden. The description mentions no parameters at all, so the baseline 3 applies.

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 description states a specific verb and resource ("Create a new product listing") and adds audience scope with "(seller tool)". It is clear what the tool does, though it never distinguishes itself from peers like bulk_update_listings or search_inventory beyond the seller-facing framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no naming of alternatives (e.g., bulk_update_listings for edits). The parenthetical audience hint implies a seller context but leaves the agent to infer when creation is appropriate.

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?