Skip to main content
Glama

Poshmark Sold Search

poshmark_sold_search
Read-onlyIdempotent

Search Poshmark SOLD listings and return realized/ask-at-sale prices, the best open sold-price comp data on Poshmark (no login, no API key). Sourced live from poshmark.com/search?availability=sold_out. Returns up to ~48 results per call (one page, no pagination cursor). price is the listing price shown on the sold post, as Poshmark reports it, not an independently verified receipt.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 10,
      "query": "lululemon align",
      "sort_by": "relevance"
    },
    "name": "poshmark_sold_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, 1-48 (default 24)
queryYesSearch text, e.g. "lululemon align leggings" or "coach tabby bag"
sort_byNorelevance (default) | price_desc | price_asc
departmentNoOptional department filter as Poshmark spells it, e.g. "Women", "Men", "Kids", "Home"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description adds real value beyond them: no auth required, one page capped at ~48 results with no pagination cursor, and a caveat that `price` is the posted sold price rather than a verified receipt. That last point is a meaningful data-quality disclosure. It stops short of describing result ordering or failure modes.

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?

Three tight sentences, front-loaded with the core action and scope, followed by sourcing and the price caveat. No filler or repetition.

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

Completeness4/5

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

With no output schema, the description does the work of explaining what comes back (prices, up to ~48 results, single page) and the reliability caveat on price. It could say more about result shape or sort behavior, but it is sufficient for correct invocation.

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 all four parameters (query, limit, sort_by, department) are already documented with examples. The description adds only the implicit ~48 cap on results, which the schema's limit range already conveys. Baseline 3 is appropriate.

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 ('Search Poshmark SOLD listings') plus the exact data returned (realized/ask-at-sale prices). The 'SOLD' qualifier cleanly separates it from an active-listing search without needing to name the sibling.

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?

Frames the tool as 'the best open sold-price comp data on Poshmark' and notes no login/API key, which implies comps/resale-price use. However, it never explicitly says when to choose this over poshmark_active_search or other alternatives, leaving the routing to inference.

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.