Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

poshmark_category

Browse Poshmark listings by category path and paginate results using next_max_id as max_id to fetch additional pages via Crawlora MCP.

Instructions

Browse Poshmark listings by category. Returns a page of Poshmark listings for a given category path (e.g. Women-Shoes, Men-Shirts), the same browsing view as Poshmark's own category pages. Pass a previous response's next_max_id back as max_id to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
pathYesPoshmark category path segment, e.g. Women-Shoes, Men-Shirts
max_idNoOpaque pagination cursor from a previous response's next_max_id. Omit for the first page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the result is a single page of listings and explains the pagination loop, which is valuable, but says nothing about auth requirements, rate limits, page size, or what happens with an invalid path.

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 compact sentences, front-loaded with the purpose and followed by the return shape and pagination hint. No filler, though the parenthetical examples and the 'same browsing view' clause are somewhat redundant with the schema.

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

Completeness3/5

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

There is no output schema and no annotations, so the description should carry more weight. It states that a page of listings is returned and how to paginate, but does not sketch what a listing contains or other operational constraints, leaving it adequate but thin for a paginated browse endpoint.

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 both parameters (path and max_id) are already documented in the schema, including examples and the cursor's origin. The description repeats the same information rather than adding new meaning, so baseline 3 applies.

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?

The description names a specific verb and resource (browse Poshmark listings by category) and clarifies the browsing view matches Poshmark's own category pages. It is clear but does not explicitly differentiate itself from sibling tools like poshmark_search or poshmark_categories, so an agent must infer the boundary.

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?

It gives concrete usage guidance for pagination ('Pass a previous response's next_max_id back as max_id'), which is genuinely useful. However, it never states when to choose this tool over poshmark_search or poshmark_categories, leaving the routing decision implied by the category-path requirement.

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