Skip to main content
Glama

Server Details

What secondhand clothes, shoes and bags actually sold for on Poshmark, plus buy or pass verdicts.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A3.6/5.0

Scored across 2 tools

Disambiguation4/5

buy_or_pass is a decision-layer tool while sold_comps is a raw data-retrieval tool, so an agent can tell which to call for a 'should I buy' vs 'what did it sell for' question. There is mild overlap since buy_or_pass internally consumes sold comps and accepts the same size/condition filters, but the output types (verdict vs statistics) are clearly distinct.

Naming Consistency3/5

Both names use snake_case, so casing is consistent, but the conventions differ: buy_or_pass is an action/decision phrase while sold_comps is a noun phrase describing a dataset. Neither follows a verb_noun pattern, making the pairing readable but not predictable as a set.

Tool Count3/5

Two tools is thin for a reselling assistant, though each is substantive rather than trivial and buy_or_pass layered on sold_comps is a coherent pairing. It sits at the borderline where an agent gets a decision plus its evidence but no exploratory surface.

Completeness3/5

The core loop of comps-to-verdict is covered, but there is no tool for active/competing listings or market supply, which materially affects a resale buy decision, and no way to save or revisit past evaluations. Filtering (size, condition, recency) is well covered, so gaps are notable rather than crippling.

Available Tools

2 tools
buy_or_passInspect

Whether an item is worth buying at a given cost to resell on Poshmark: BUY, MAYBE or PASS with the reason, judged from its clean sold comps after Poshmark's fee. Call it for one item at a time; if it reports busy, wait the given number of seconds and call again.

    query: brand + item, e.g. "patagonia better sweater".
    cost: what you'd pay, e.g. the thrift-store tag price in USD.
    min_profit: smallest profit after fees worth the effort (default 10).
    size / condition: same filters as sold_comps.
    source: "poshmark" (the only live marketplace today).
    
ParametersJSON Schema
NameRequiredDescriptionDefault
costYes
sizeNo
queryYes
sourceNoposhmark
conditionNo
min_profitNo
sold_compsInspect

What an item actually sold for on Poshmark: median sold price, typical range (p10-p90), days to sell, what the seller keeps after fees, price by condition, a confidence rating, and the matching sales. Call it for one item at a time; if it reports busy, wait the given number of seconds and call again.

    query: brand + item, e.g. "coach tabby 26" or "lululemon align leggings", or a plain item type like
        "womens jeans". For kids' clothing put girls, boys, kids, toddler or youth in the query ("girls jeans");
        otherwise kids' sizes are removed.
    size: only this size, e.g. "8", "M" or "10.5". Leave it out unless the user named a size: it can leave
        very few sales.
    condition: "new", "used", or an exact grade: new_with_tags, not_new_with_tags, used_like_new,
        used_excellent, used_good, used_fair (comma-separated for several).
    days: only sales from the last N days (1-365).
    limit: how many individual sales to include (0-50).
    deep: true reads up to ~190 recent sales instead of 48 (slower when not cached, about 10s; one lookup).
    source: "poshmark" (the only live marketplace today).
    
ParametersJSON Schema
NameRequiredDescriptionDefault
daysNo
deepNo
sizeNo
limitNo
queryYes
sourceNoposhmark
conditionNo

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedsold_comps1 field changed
      • addedInput schema / properties / deep
        Added value: +{
        +  "default": false,
        +  "title": "Deep",
        +  "type": "boolean"
        +}
  2. 2 tool updates
    • Changedbuy_or_pass1 field changed
      • addedInput schema / properties / source
        Added value: +{
        +  "default": "poshmark",
        +  "title": "Source",
        +  "type": "string"
        +}
    • Changedsold_comps1 field changed
      • addedInput schema / properties / source
        Added value: +{
        +  "default": "poshmark",
        +  "title": "Source",
        +  "type": "string"
        +}
  3. 2 tool updates
    • First observedbuy_or_pass
    • First observedsold_comps

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources