Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

poshmark_search

Search Poshmark clothing, shoe, and accessory listings to retrieve item summaries with price, brand, size, condition, seller, and images, plus total count and pagination cursor for next page.

Instructions

Search Poshmark listings. Searches Poshmark for clothing, shoes, and accessory listings, returning listing summaries (title, price, brand, size, condition, seller, images) plus the total matching count and an opaque pagination cursor. Pass a previous response's next_max_id back as max_id to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
queryYesFree-text keyword search
max_idNoOpaque pagination cursor from a previous response's next_max_id. Omit for the first page
departmentNoDepartment filter, e.g. Women, Men, Kids

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries full behavioral burden, and it delivers: it enumerates the returned summary fields (title, price, brand, size, condition, seller, images), the total match count, and the opaque pagination cursor contract. It omits rate limits, auth, or result-size caps, keeping it short of a 5 for an unannotated tool.

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 that are front-loaded with the core purpose and follow with return shape and pagination. There is minor redundancy between 'Search Poshmark listings' and 'Searches Poshmark for ... listings', but overall it is tight and well ordered.

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 usefully describes the return payload (summary fields, total count, cursor) so the agent knows what comes back, and it explains pagination. The main gap is the absence of any guidance on when to prefer sibling Poshmark tools, which for a large sibling set would be valuable.

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 query, max_id, and department. The description restates the max_id/next_max_id pagination mapping and the department concept, adding little beyond what the schema fields already say. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) plus resource (Poshmark listings) and narrows the scope to clothing, shoes, and accessories. An agent can distinguish it as a listing-search tool rather than a detail/lookup tool, though it does not explicitly name the sibling it is not (e.g. poshmark_listing or poshmark_closet).

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 clear context for one specific usage detail – paginating with next_max_id via max_id – but offers no explicit when-to-use vs. when-not or routing to sibling tools like poshmark_brand or poshmark_category for filtered browsing. Usage is left to inference for a first-page 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