Skip to main content
Glama

Poshmark Active Search

poshmark_active_search
Read-onlyIdempotent

Search Poshmark ACTIVE (currently listed, not yet sold) listings, for comparing current ask prices against poshmark_sold_search results. No login, no API key. Returns up to ~48 results per call.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 10,
      "query": "leggings",
      "department": "Women"
    },
    "name": "poshmark_active_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, 1-48 (default 24)
queryYesSearch text, e.g. "lululemon align leggings"
sort_byNorelevance (default) | price_desc | price_asc
departmentNoOptional department filter, e.g. "Women", "Men", "Kids", "Home"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds two useful facts not in annotations: no login/API key required, and an approximate result ceiling ('up to ~48 results per call'), though that partly restates the schema's limit max of 48. Pagination behavior beyond that cap and any rate limits are left unstated.

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?

A single front-loaded sentence that leads with the verb and the key scope distinction, then adds the comparison purpose and access constraints. No filler, and nothing important is buried.

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 four-parameter read-only search with no output schema, the definition covers scope, purpose, auth requirements and result volume. The remaining gap is that result fields are never characterized beyond the implied ask price, which matters slightly more because no output schema exists to describe them.

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%, with each of the four parameters documented in-schema, so the baseline is 3. The description adds no syntax, format or defaulting guidance for query, department, sort_by or limit beyond what the schema already provides.

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 and resource (search Poshmark active listings) and disambiguates scope explicitly: 'ACTIVE (currently listed, not yet sold)'. It also names the complementary sibling poshmark_sold_search, so an agent can tell active vs sold retrieval apart without opening either schema.

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

Usage Guidelines4/5

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

The description gives a clear use context — 'comparing current ask prices against poshmark_sold_search results' — which tells the agent when this tool is the right choice and points at the alternative. It stops short of stating exclusions or prerequisites (e.g., what to do if no results are returned, or when to skip active search entirely).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.