Skip to main content
Glama

NeuralVerge Business Intelligence

by ai.neuralverge.api
OverviewDiscussionsAdmin

Poshmark user items

run_poshmark_users_items

Listings in a Poshmark closet by username or URL, with department, category, brand, size, color, price, condition, shipping, availability and sort filters. 1 point per returned record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoSizes (comma separated). e.g. 8, M
sortNoSort by. Options: relevance = Relevance, just_in = Just in, price_low_to_high = Price: low to high, price_high_to_low = Price: high to low
userYesUsername or closet URL. e.g. Username or closet URL, e.g. najescloset
brandNoBrand. e.g. Nike, Coach
colorNoColors
domainNoDomain. Options: poshmark.com = poshmark.com, poshmark.ca = poshmark.ca Default: poshmark.com.
categoryNoCategory. e.g. Shoes, Dresses, Bags
shippingNoShipping. Options: free = Free shipping, discounted = Discounted shipping
conditionNoCondition. Options: all = All conditions, nwt = New with tags (NWT)
max_itemsNoMax items (up to 500) Default: 25.
price_maxNoMax price
price_minNoMin price
departmentNoDepartment. Options: Women = Women, Men = Men, Kids = Kids, Home = Home, Electronics = Electronics, Pets = Pets, Beauty & Wellness = Beauty & Wellness
start_pageNoStarting page
subcategoryNoSubcategory. e.g. Athletic Shoes, Sneakers
availabilityNoAvailability. Options: all = All, available = Available, available_and_dropping_soon = Available and dropping soon, dropping_soon = Dropping soon, sold = Sold, not_for_sale = Not for sale

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / brand / description
      Previous value: -"Brand. e.g. e.g. Nike, Coach"New value: +"Brand. e.g. Nike, Coach"
    • changedInput schema / properties / category / description
      Previous value: -"Category. e.g. e.g. Shoes, Dresses, Bags"New value: +"Category. e.g. Shoes, Dresses, Bags"
    • changedInput schema / properties / size / description
      Previous value: -"Sizes (comma separated). e.g. e.g. 8, M"New value: +"Sizes (comma separated). e.g. 8, M"
    • changedInput schema / properties / subcategory / description
      Previous value: -"Subcategory. e.g. e.g. Athletic Shoes, Sneakers"New value: +"Subcategory. e.g. Athletic Shoes, Sneakers"
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so description carries the full burden. It discloses pricing ('1 point per returned record'), which is useful behavioral context, and it enumerates filter fields. But it doesn't describe pagination behavior across start_page/max_items (up to 500), rate limits, or whether results include sold items by default.

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?

Single dense sentence front-loads the core purpose and the pricing note. It is efficient, though the long enumeration of filters is somewhat redundant with a 16-param 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?

For a 16-param list tool with no annotations and no output schema, this description covers purpose and filters but leaves pagination semantics, default availability (sold/nft), and result shape unaddressed. Adequate but with visible gaps.

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 every parameter (including enum explanations and defaults). The description only re-lists filter categories already captured in the schema. Baseline 3 applies.

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 (list) and resource (Poshmark closet listings) with the key selector (username or URL). Clearly distinguished from siblings run_poshmark_items_search (search-driven) and run_poshmark_users (user profiles) by anchoring to a specific 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?

Implying the tool is for enumerating a known seller's closet, but no explicit when-to-use vs run_poshmark_items_search or run_poshmark_users. Usage is inferable from the required 'user' parameter and description, but alternatives aren't named.

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

All NeuralVerge Business Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources