Skip to main content
Glama

Make an offer

make_offer

Send the seller an offer below the listed price, with an optional note. The seller has 24 hours to accept, decline or counter; check with offer_status. If accepted, start_purchase uses the agreed price. Returns the offer id, its status and when it expires. Respect the listing's minimum_offer from get_listing. Requires a Port66 session.

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": {
      "id": "<id>",
      "amount_usd": "<amount_usd>"
    },
    "name": "make_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure').
messageNoA short, polite note to the seller (optional, up to a few sentences).
amount_usdYesThe price offered for the piece, in US dollars, before shipping.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / amount_usd / description
      Previous value: -"Offered price in USD"New value: +"The price offered for the piece, in US dollars, before shipping."
    • changedInput schema / properties / id / description
      Previous value: -"Listing id (the slug from search_listings)"New value: +"The listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure')."
    • addedInput schema / properties / id / minLength
      Added value: +1
    • changedInput schema / properties / message / description
      Previous value: -"A short, polite note to the seller"New value: +"A short, polite note to the seller (optional, up to a few sentences)."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare that this writes and is not destructive; the description adds substantive context beyond that — a 24-hour seller response window, the three possible seller actions, the expiry timestamp returned, and the session requirement. It omits whether an offer can be withdrawn or whether one offer per listing is enforced, which are the remaining behavioral unknowns for a mutation tool.

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?

Four dense sentences, front-loaded with the action and constraint, then flow routing, then return shape, then prerequisites. Every sentence carries distinct information with no restatement of the title or name.

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?

There is no output schema, but the description enumerates the returned fields (offer id, status, expiry), and it positions the call within the larger listing-to-purchase flow. For a three-parameter mutation tool with complete schema coverage, nothing an agent needs before calling is missing.

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 baseline is 3, but the description adds real semantics: the amount must sit below the listed price and at or above the listing's minimum_offer, which constrains the value far beyond the schema's minimum of 1. The note parameter's purpose is already fully covered by the schema.

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?

The description opens with a specific verb and resource ('Send the seller an offer below the listed price') and includes the optional note. It is immediately distinguishable from siblings offer_status and start_purchase, which are named with their role in the flow.

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

Usage Guidelines5/5

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

It names alternatives and the conditions that select them: use offer_status to check the 24-hour window, use start_purchase once accepted, and respect the listing's minimum_offer from get_listing. The 'Requires a Port66 session' prerequisite is stated explicitly, so there is little left to infer.

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