Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

depop_search

Search Depop resale listings by keyword and filter by price, size, brand, condition, color, and category. Returns listing summaries with pagination and total matches.

Instructions

Search Depop listings. Searches Depop's resale-fashion marketplace by free-text keyword, with optional price, condition, colour, category, subcategory, gender, kids-department, brand, discount, and sort filters, returning listing summaries (title, price, brand, condition, like count, photos, sizes), a pagination cursor, and the total matching count.

Input Schema

NameRequiredDescriptionDefault
sortNoSort order: relevance, price_low_to_high, price_high_to_low
afterNoOpaque pagination cursor from a previous response's next_cursor field. Omit for the first page.
queryYesFree-text keyword search
sizesNoComma-separated Depop size composite ids (format {size_set_id}.{id}, e.g. \
genderNoDepartment filter: female, male
coloursNoComma-separated colour filter: black, grey, white, brown, tan, cream, yellow, red, burgundy, orange, pink, purple, blue, navy, green, khaki, multi
is_kidsNoKids-department filter: true restricts results to kids items only, false excludes them, omitted returns both.
on_saleNoRestrict results to discounted listings
categoryNoDepop category slug: tops, bottoms, dresses, coats-jackets, jumpsuit-and-playsuit, suits, footwear, accessories, nightwear, underwear, swim-beach-wear, fancy-dress, sleepsuits-and-bodysuits, bundles, beauty, face-masks, home, tech-accessories, film, art, books-and-magazine, music, party-supplies, sports-equipment-accesories, toys, umbrella. See GET /depop/categories for a machine-readable enumeration with names and subcategories.
brand_idsNoComma-separated Depop internal numeric brand ids. Not documented by Depop -- find a brand's id by browsing its depop.com/brands/<slug>/ page.
conditionNoComma-separated condition filter: brand_new, used_like_new, used_excellent, used_good, used_fair
price_maxNoMaximum listing price in USD
price_minNoMinimum listing price in USD
subcategoryNoComma-separated Depop subcategory slug(s), scoped within category. See GET /depop/categories for the full list per category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.0
    • addedInput schema / properties / is_kids
      Added value: +{
+  "description": "Kids-department filter: true restricts results to kids items only, false excludes them, omitted returns both.",
+  "type": "boolean"
+}
    • addedInput schema / properties / sizes
      Added value: +{
+  "description": "Comma-separated Depop size composite ids (format {size_set_id}.{id}, e.g. \\",
+  "type": "string"
+}
  2. Added

TDQS

A3.5/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 behavioral burden. It does disclose the return shape (listing summaries with title, price, like count, sizes) plus a pagination cursor and total count, which is genuinely useful. It says nothing about auth, rate limits, or result caps, so it is adequate but incomplete.

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?

The definition is front-loaded with the core purpose and packs filters and return values into one dense but non-redundant sentence. Every clause carries information; only the slight density keeps it from a 5.

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 14-parameter search tool with full schema coverage and no output schema, the description covers the important ground: what it searches, what filters exist, and what comes back including pagination. It omits only edge behavior such as result limits or empty-result handling.

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 the schema already documents all 14 parameters including enum-like value lists. The description only paraphrases the filter categories without adding syntax, format, or default details beyond the schema, so the baseline 3 applies.

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+resource ("Search Depop listings") and expands to name the marketplace and that it is free-text keyword driven with filters. It is easy to distinguish from depop_item_similar or depop_suggest, though it never explicitly names a sibling tool to route against, keeping it 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 Guidelines3/5

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

Usage is implied by "free-text keyword" and the filter list, which tells the agent this is the keyword-driven entry point. However, there is no explicit when-to-use vs. when-not, and no routing to siblings like depop_search_sellers or depop_search_facets, so guidance stays at the implied level.

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