NeuralVerge Business Intelligence

Poshmark items search

run_poshmark_items_search

Search live Poshmark listings by keyword with department, category, brand, size, color, price, condition, shipping, availability and sort filters. 1 point per returned record.

Input Schema

TableJSON Schema

Name	Required	Description
`size`	No	Sizes (comma separated). e.g. 8, M
`sort`	No	Sort by. Options: relevance = Relevance, just_in = Just in, price_low_to_high = Price: low to high, price_high_to_low = Price: high to low
`brand`	No	Brand. e.g. Nike, Coach
`color`	No	Colors
`query`	No	Search term (optional). e.g. nike shoes
`domain`	No	Domain. Options: poshmark.com = poshmark.com, poshmark.ca = poshmark.ca Default: poshmark.com.
`category`	No	Category. e.g. Shoes, Dresses, Bags
`shipping`	No	Shipping. Options: free = Free shipping, discounted = Discounted shipping
`condition`	No	Condition. Options: all = All conditions, nwt = New with tags (NWT)
`max_items`	No	Max items (up to 500) Default: 25.
`price_max`	No	Max price
`price_min`	No	Min price
`department`	No	Department. Options: Women = Women, Men = Men, Kids = Kids, Home = Home, Electronics = Electronics, Pets = Pets, Beauty & Wellness = Beauty & Wellness
`start_page`	No	Starting page
`subcategory`	No	Subcategory. e.g. Athletic Shoes, Sneakers
`availability`	No	Availability. 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.

Changed4 schema fields changedOct 7, 2026

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"

AddedOct 1, 2026

TDQS

B3.3/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, and it does disclose a real behavioral trait: '1 point per returned record' (billing/cost model). However, it omits auth requirements, rate limits, and pagination behavior considerations even though start_page exists in the schema.

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?

Two short sentences with zero waste; the core purpose is front-loaded and the cost note is appended efficiently. Every clause earns its place.

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-parameter tool with no annotations and no output schema, the description covers purpose and cost but does not describe the returned record shape or pagination semantics implied by start_page/max_items. It is adequate but leaves gaps an agent may need.

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 every parameter is already documented inline, including enums and defaults. The description only restates the filter categories and adds no syntax, format, or interaction detail beyond the schema, making the baseline 3 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) and resource (live Poshmark listings) and enumerates the filter dimensions available, so the agent understands scope well. It does not, however, distinguish itself from siblings such as run_poshmark_items (single-item fetch) or run_poshmark_users_items, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The word 'live' hints at current availability versus sold listings, but the agent must infer when to prefer this over run_poshmark_users_items or a direct run_poshmark_items lookup.

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 tools Inspect

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

Need Help?