Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

poshmark_trend

Browse a Poshmark trend or showroom collection: fetch a page of listings by id, then pass max_id to get the next page.

Instructions

Browse a Poshmark trend/showroom collection. Returns a page of Poshmark listings for a curated trend/showroom collection (e.g. "Vintage Celine Handbags"), the same browsing view as Poshmark's own trend pages. Pass a previous response's next_max_id back as max_id to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
idYesPoshmark trend/showroom id, the trailing id segment of a /trend/{slug}-{id} 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 of behavioral disclosure. It usefully states that the tool returns a page of listings and supports cursor pagination, but it does not explicitly declare read-only safety, permissions, rate limits, or error behavior. 'Browse' implies a read operation, but this is not formalized.

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?

The description is three sentences, front-loaded with the core purpose and followed by return and pagination details. Every sentence earns its place, and there is no redundant or filler 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?

For a two-parameter browsing tool with no output schema and no annotations, the description covers the essential behavior: it explains that a page of listings is returned and how to paginate. It does not elaborate on listing fields or auth, but the schema already documents the id format and max_id cursor, so the description is largely complete.

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 are already well documented. The description adds a concrete example collection name for id and restates the pagination contract for max_id, but it does not add meaningful syntax or format details beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: 'Browse a Poshmark trend/showroom collection' and returns a page of listings for a curated trend/showroom collection. It is clear enough to distinguish this from generic Poshmark listing tools, though it does not explicitly name sibling alternatives such as poshmark_search or poshmark_category.

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 pagination guidance is explicit: pass a previous response's next_max_id as max_id to fetch the next page. However, the description does not state when to use this tool versus poshmark_search, poshmark_category, or other Poshmark browsing tools. Usage is implied by the resource name rather than by explicit selection criteria.

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