Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

poshmark_closet

Fetch a Poshmark seller's closet to get public profile stats, listing count, and first-page items; pass max_id to retrieve additional listing pages.

Instructions

Get Poshmark seller closet (storefront). Returns a Poshmark closet (seller storefront) page: the seller's public profile and reputation stats (followers, ratings, items sold) plus a first page of their currently available listings and total listing count. Pass a previous response's next_max_id back as max_id to fetch the next page of listings; paginated responses omit the seller profile, so fetch without max_id first to get seller fields.

Input Schema

NameRequiredDescriptionDefault
max_idNoOpaque pagination cursor from a previous response's next_max_id. Omit for the first page
usernameYesPoshmark seller username, the path segment of a /closet/{username} URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return contents (profile, reputation stats, listings, total count) and a non-obvious behavioral quirk — paginated responses omit the seller profile, so ordering matters. It omits auth/rate-limit context, which is a minor gap.

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

Conciseness4/5

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

Three sentences, front-loaded with the tool's purpose, then return contents, then pagination mechanics. Efficient overall, with only mild redundancy between 'Poshmark seller closet (storefront)' and 'a Poshmark closet (seller storefront)'.

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?

No output schema or annotations exist, so the description must explain returns, which it does thoroughly, including the pagination caveat. It is complete enough for correct invocation, missing only peripheral details like authentication expectations.

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. The description adds meaning beyond the schema by tying max_id to a prior response's next_max_id and stating the sequencing constraint that the first call must omit it to obtain seller fields, which the schema does not convey.

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+resource ('Get Poshmark seller closet (storefront)') and enumerates exactly what is returned: seller profile, reputation stats, first page of listings, and total count. This clearly distinguishes it from siblings like poshmark_listing (single item) and poshmark_search.

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 concrete procedural guidance: 'fetch without max_id first to get seller fields' and pass a previous response's next_max_id back as max_id. It clearly explains the pagination workflow, though it does not explicitly contrast when to choose this tool over siblings such as poshmark_search.

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

Deploy Server

Other Tools