Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

poshmark_brand

Browse Poshmark listings by brand and paginate through results. Pass a brand name to fetch a page, then use its next_max_id as max_id for the next page.

Instructions

Browse Poshmark listings by brand. Returns a page of Poshmark listings for a given brand name (e.g. Nike), the same browsing view as Poshmark's own brand pages. Pass a previous response's next_max_id back as max_id to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
nameYesPoshmark brand name, matching the path segment of a /brand/{name} URL
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

A3.6/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 burden. It discloses that the result is a paginated page of listings and how to advance pages, and 'Browse'/'Returns a page' implies a read-only operation. It stops short of stating permission/auth requirements or rate limits, so it is adequate but not rich.

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 sentences, each earning its place: purpose, return shape, and pagination. The core action is front-loaded with no filler.

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?

For a simple browse tool with no output schema, the description covers purpose, return shape, and pagination adequately. It would be complete if it flagged sibling alternatives, but nothing essential to invoking it is missing.

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 coverage is 100%, so both name and max_id are already documented with format and examples. The description restates the pagination contract ('pass next_max_id back as max_id') and adds a Nike example, adding marginal value over the schema but not new meaning.

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+resource ('Browse Poshmark listings by brand') and clarifies it returns a page of listings for a given brand. It implicitly distinguishes itself from poshmark_brands (which lists brand names), but never names that sibling or poshmark_search to make the distinction explicit.

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?

The description conveys the browsing context ('by brand', 'same browsing view as Poshmark's own brand pages') and how to paginate, which implies when to use it. However, it never states when to prefer it over poshmark_search or poshmark_brands, 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.

Deploy Server

Other Tools