Skip to main content
Glama

Find eBay listings under market

find_underpriced
Read-only

Live eBay US Buy It Now listings of an item priced under what the same item actually sells for. Use when the user wants to buy something below market. One search runs, as in get_sold_comps (the query as typed, model or part_number appended when missing; with no query, brand plus model or part number): the recent sold prices give the usual price (soldBaseline: typicalPrice, the range and how many sales), then the live listings for the same words are checked title by title and only the same item is kept (other models, lots and accessories are left out, and for-parts listings unless condition asks for them). A deal's total is price plus shipping when eBay gives shipping; it is at least 15% under the usual price for its condition, or, with max_price, at or under max_price (shipping shown) and at least 5% under the usual price. Up to 10 deals, best discount first, each with title, price, shipping, condition, seller feedback, how far under (say) and the listing link. Prices in USD. When deals carry links, disclosure is a sentence the user must see.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_underpriced"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoThe brand or maker exactly as printed on the item, its tag or its label (for example "Simrad", "Pyrex", "Levi's"). Fill it from what you read on the item or the user's photo; leave it empty rather than guess.
modelNoThe model or product-line name as printed on the item or its box (for example "iPhone 12", "QuietComfort 35", "Odyssey G5", "501"). It is passed to the identification as a hint and added to the search when no word of it is already there; it never replaces the search. Put a manufacturer part number in part_number. Leave it empty rather than guess.
queryNo3 to 6 specific words, brand and model first, like an eBay search.
conditionNoOnly listings in this condition, measured against sales in the same condition. Leave empty for new and used; for-parts listings are shown only when this asks for them.
max_priceNoThe most the user wants to pay in USD, shipping included when eBay shows it. With it, a listing qualifies at or under this price with its shipping shown and at least 5% under the usual price; without it, at least 15% under the usual price.
part_numberNoThe manufacturer part number printed on the label or rating plate (for example "000-16294-001", "DCD771C2", "CUH-ZCT2U"), copied character for character. Not a size, voltage, year, SKU, ASIN, LPN or barcode. In price_item it is a hint to the identification only and is not added to the search (a part number required in every listing title leaves too few sales); in get_sold_comps it is appended to the query when the query lacks it. Leave it empty rather than guess.

Output Schema

NameRequiredDescriptionDefault
noteNo
textNo
dealsNoLive listings priced under the usual sale price.
queryNo
sourceNoAttribution to show the user.
checkedNo
currencyNo
maxPriceNo
conditionNo
moreDealsNo
disclosureNo
marketplaceNo
soldBaselineNoWhat the item usually sells for.
unstructuredNoTrue: read `text`.
searchedQueryNo
affiliateLinksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "affiliateLinks": {
      +      "type": "boolean"
      +    },
      +    "checked": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "liveListings": {
      +          "type": "number"
      +        },
      +        "sameItem": {
      +          "type": "number"
      +        },
      +        "sameItemCheckFinished": {
      +          "type": "boolean"
      +        },
      +        "sentToSameItemCheck": {
      +          "type": "number"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "condition": {
      +      "type": "string"
      +    },
      +    "currency": {
      +      "type": "string"
      +    },
      +    "deals": {
      +      "description": "Live listings priced under the usual sale price.",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "disclosure": {
      +      "type": "string"
      +    },
      +    "marketplace": {
      +      "type": "string"
      +    },
      +    "maxPrice": {
      +      "type": "number"
      +    },
      +    "moreDeals": {
      +      "type": "number"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "query": {
      +      "type": "string"
      +    },
      +    "searchedQuery": {
      +      "type": "string"
      +    },
      +    "soldBaseline": {
      +      "additionalProperties": {},
      +      "description": "What the item usually sells for.",
      +      "properties": {
      +        "range": {
      +          "additionalProperties": {},
      +          "properties": {
      +            "high": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "low": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "p25": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "p75": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "relevanceChecked": {
      +          "type": "boolean"
      +        },
      +        "sales": {
      +          "type": "number"
      +        },
      +        "salesIsLowerBound": {
      +          "type": "boolean"
      +        },
      +        "typicalPrice": {
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "source": {
      +      "additionalProperties": {},
      +      "description": "Attribution to show the user.",
      +      "properties": {
      +        "cite": {
      +          "description": "A sentence to show the user, naming where the price came from.",
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "url": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "text": {
      +      "type": "string"
      +    },
      +    "unstructured": {
      +      "description": "True: read `text`.",
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say read-only, open-world, non-idempotent; the description goes far beyond by disclosing the two-stage pipeline (sold comps baseline, then title-by-title filtering of live listings), the exclusion rules (other models, lots, accessories, for-parts unless requested), the 15%/5% discount thresholds, that total includes shipping, the 10-result cap with best-discount-first ordering, and the USD currency plus mandatory disclosure sentence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded with purpose and most sentences carry real information, but the middle is a dense run-on with nested parentheticals (the search-behavior clause in particular) that forces re-reading. A short bulleted split between search behavior, qualification rules, and output would preserve the content with less parsing cost.

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?

Despite six parameters and a multi-stage pipeline, the description covers search construction, filtering, deal qualification, result ordering, per-deal fields, currency, and the disclosure obligation, and an output schema exists to carry return-value detail. Nothing an agent needs to call it correctly appears to be 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 the baseline is 3, but the description adds cross-parameter behavior the schema does not: how model is appended only when missing, how query falls back to brand plus model or part number, and how condition changes the comparison baseline and the for-parts filtering. Some max_price wording repeats the schema, which keeps it short of 5.

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?

States a specific verb and resource with scope: "Live eBay US Buy It Now listings of an item priced under what the same item actually sells for." It also distinguishes itself from the sold-comps sibling by contrasting live listings against sold prices, so an agent can tell what it returns without opening the schema.

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?

Gives an explicit trigger: "Use when the user wants to buy something below market," and explains the max_price branch that changes qualification criteria. It does not state exclusions or name which sibling to use instead when the user wants valuation rather than a purchase (e.g., price_item or worth_it), so routing is clear but not fully closed.

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