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. Dates show when Glama detected each change.

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

B3.1/5.0

Behavior2/5

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

The description adds no behavioral detail beyond what annotations already provide: no explanation of side effects, listing visibility, duplicate/SKU behavior, auth requirements, or validation outcomes. It does not contradict the annotations, but it does not meaningfully increase transparency.

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 description is one concise, front-loaded sentence with no filler or repeated examples. It is short but appropriately structured for a tool whose detailed requirements live in the schema.

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

Completeness3/5

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

The schema, output schema, and annotations make the tool callable, but the description omits usage context, behavioral expectations, and relationships to sibling tools. It is minimally viable but not genuinely complete for an agent facing a variety of seller tools.

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%, so the schema fully documents all parameters. The description itself mentions no parameters, but the baseline of 3 applies because the structured schema carries the semantic burden.

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 clearly identifies the action ('Create') and the resource ('new product listing'), and adds seller context. It distinguishes creation from sibling update tools, though it largely restates the title with only a little extra scope information.

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 explicit guidance about when to use this tool versus bulk_update_listings or other seller tools, and no mention of prerequisites or alternatives. The word 'new' hints at create-vs-update, but that is minimal and not helpful enough.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Most tools target distinct resource/action pairs: search vs details, quote request vs response, bulk export vs bulk ship. The main overlaps are get_quote_requests vs seller_inbox_summarise and quick_buy vs request_quote, but their descriptions provide enough boundary to avoid serious misselection.

Naming Consistency4/5

The majority of tools follow a verb_noun pattern with a clear bulk_ prefix for bulk operations. Minor deviations like quick_buy and seller_inbox_summarise (object before verb) slightly break the pattern, but the naming remains broadly predictable.

Tool Count5/5

12 tools is well within the ideal range for a two-sided marketplace server. Each tool covers a meaningful seller or buyer workflow without feeling redundant or bloated.

Completeness3/5

Core workflows are covered: search, product details, quote negotiation, listing creation, bulk updates, bulk shipping, and export. Notable gaps include no single listing delete/update, no buyer-facing order or quote status tool, and no action to resolve reported issues surfaced by seller_inbox_summarise.

Resources

Need Help?