Skip to main content
Glama

Soldgraph

by io.github.soldgraph
OverviewDiscussionsAdmin

Poshmark active listings

poshmark_listings
Read-onlyIdempotent

Search one page of Poshmark active listings by keyword, on Poshmark US or Canada, in the sort order you pick. Pages use a cursor. Results are cached for 15 minutes. Each completed search costs 1 request, cache hits included; failed searches are free. Docs: https://soldgraph.com/docs/api/poshmark-listings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch keywords, 1–200 characters, as you'd type them into the marketplace's search box. Be specific: model, size, grade, edition.
pageNoSource page to fetch. Where an endpoint has cursor, pages after 1 also need it.
sortNoPoshmark's listing order. ending_soon isn't available on Poshmark and returns 422.best_match
cursorNoThe previous page's next_cursor. Leave it out on page 1. Required on every later page.
fieldsNosummary keeps the fields most agents need; full returns every field the API returns.summary
countryNoWhich Poshmark site to search: us (poshmark.com, US dollars) or ca (poshmark.ca, Canadian dollars). Results, prices, min_price and max_price use that site's currency. Optional.us
conditionNoOne of Poshmark's own condition codes: nwt (new with tags), uln (like new), ug (good) or uf (fair). Rows use the same codes. Poshmark filters one condition at a time, so more than one returns 422.
max_priceNoHighest price, in whole units of the country's currency (US dollars for us). Optional. You can send it without min_price.
min_priceNoLowest price, in whole units of the country's currency (US dollars for us). Optional. Must not be more than max_price. You can send it without max_price.

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?

Adds substantive traits the annotations don't carry: 15-minute result caching, request-cost accounting including cache hits and free failures, and cursor-based pagination. It stops short of disclosing result volume per page, rate limits, or error behavior beyond the 422 note embedded in the schema.

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 tight sentences plus a docs link, front-loaded with the core action and scope before cost and pagination details. No filler or repeated schema content.

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?

Covers scope, pagination, cost and caching for a 9-parameter read tool with no output schema. The main omission is any hint of what a page returns (e.g. next_cursor availability or result counts), which matters slightly given there is no output schema to fall back on.

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 the schema already documents every parameter including enums, ranges, currency and the 422 condition rules. The description only reinforces cursor/pagination behavior, adding little beyond the structured fields — baseline 3 applies.

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 one page of Poshmark active listings by keyword'), plus the two supported marketplaces and the sort dimension. The word 'active' implicitly distinguishes it from poshmark_sold, so an agent can route between the two without opening either schema.

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?

Gives operational context ('Pages use a cursor', 15-minute cache, 1 request per completed search, failures free) but never explicitly states when to choose this over poshmark_sold or the other marketplace listing tools. Usage is implied by the word 'active' rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Soldgraph toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources