Skip to main content
Glama

ForthClear Liquidation Marketplace

Create a listing

create_listing
Idempotent

Publish a surplus lot for sale. Requires sign-in with seller access. Provide a title, category, condition, quantity, and price per unit. 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": {
      "name": "<name>",
      "category": "<category>",
      "condition": "<condition>",
      "quantity": "<quantity>",
      "price_per_unit": "<price_per_unit>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNoSeller's own stock-keeping unit, shown to buyers and used for reconciliation.
nameYesListing title shown to buyers and matched by catalogue search.
categoryYesCatalogue category. One of: electronics, apparel, home_goods, beauty, sports, kitchenware, office_supplies, toys, food_beverage, tools, other.
quantityYesUnits available in this lot.
conditionYesCondition of the goods: salvage (sold as-is), customer returns, shelf pulls, overstock, or new or refurbished.
descriptionNoListing body copy: condition detail, packaging, lot composition. Buyers filter on its presence and agents summarise it.
price_per_unitYesPrice in cents
idempotency_keyYesRequired. 8–200 characters (letters, digits, . _ : -). The same key returns the original result for 24 hours and is sent to Stripe as Idempotency-Key.
original_retail_priceNoOriginal retail price in cents

Output Schema

NameRequiredDescriptionDefault
listingYes
messageYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "Required. 8–200 characters (letters, digits, . _ : -). The same key returns the original result for 24 hours and is sent to Stripe as Idempotency-Key.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "category",
      -  "condition",
      -  "quantity",
      -  "price_per_unit"
      -]New value: +[
      +  "name",
      +  "category",
      +  "condition",
      +  "quantity",
      +  "price_per_unit",
      +  "idempotency_key"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / condition / description
      Previous value: -"Standard liquidation condition grade (Task #72)"New value: +"Condition of the goods: salvage (sold as-is), customer returns, shelf pulls, overstock, or new or refurbished."
  3. Changed1 schema field changed
    • 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"
      +}
  4. Changed6 schema fields changed
    • 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."
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond annotations by disclosing the seller:write scope, the OAuth discovery endpoint, and that the call is sensitive and requires per-invocation user approval. Those approval and auth requirements are exactly the kind of behavior annotations cannot express. It still says nothing about what state the resulting listing is in (e.g. live vs pending review).

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?

Three short sentences, front-loaded with the action, then requirements, then auth. The OAuth discovery URL is a slightly awkward insertion but is genuinely functional information, not filler.

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 nine-parameter creation tool with an output schema, the description covers action, authorization, scope, and approval gating, while the schema carries the field-level detail. An agent has everything needed to attempt the call correctly.

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 every parameter including idempotency_key and its Stripe forwarding is already documented. The description only restates five of the nine fields, adding no syntax or constraints beyond the schema; 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?

States a specific verb and resource: 'Publish a surplus lot for sale', which clearly separates creation from update-oriented siblings like bulk_update_listings. It does not explicitly name an alternative, so it stops short of the top score.

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

Usage Guidelines3/5

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

The precondition 'Requires sign-in with seller access' tells the agent who may call it, but there is no guidance on when to choose this over update or bulk tools, and no exclusions stated.

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