Skip to main content
Glama

Etsy Product Research: etsy/product Query API

nexscope_data_eh_etsy_product_query
Read-only

Etsy Product Research: etsy/product Query API.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (starting from 1)
isPickNoWhether to Pick the product
sortByNoSorting field (corresponding to upstream sort_by, value 1~6)
statusNoProduct status (example: 1 on the shelves, 0 off the shelves)
countryNoShipping country
categoryNoProduct classification ID (single product category), please see the product classification interface for details
endPriceNoPrice (end), which together with the starting price forms the upstream price
endSalesNoTotal sales (end)
isRavingNoWhether Raving product
pageSizeNoNumber of entries per page, maximum 100, recommended not to exceed 50
sortDescNoSorting direction (corresponds to upstream `desc`). Schema example: Descending `1`, Ascending `2`
searchKeyNoSearch keywords or Etsy product URLs
beginPriceNoPrice (start), together with the end price, form the upstream price (such as 20~100); when filling in only one side, the upstream is start~ or ~end
beginSalesNoTotal sales (starting), which together with the ending value form the upstream sales
endReviewsNoNumber of comments (end)
isBestsellNoIs it a best-selling product?
listedTimeNoThe shelf time is no earlier than this date (YYYY-MM-DD)
productTypeNoProduct type, multiple commas separated: 1=Handmade 2=Vintage 3=Digital 4=Customized 9=Other
beginReviewsNoThe number of reviews (starting), which together with the end value form the upstream reviews
currencyCodeNoCurrency code, default `USD`
endFavoritesNoNumber of collections (end)
beginFavoritesNoThe number of favorites (starting), together with the ending value, form the upstream favorites
endSalesWeeklyNoWeekly sales (end)
beginSalesWeeklyNoWeekly sales volume (start), together with the end value, form the upstream sales_weekly (such as 1~100)
endReviewsWeeklyNoNumber of new comments per week (end)
beginReviewsWeeklyNoNumber of new comments per week (start), which together with the end value form the upstream reviews_weekly
endFavoritesWeeklyNoNumber of new favorites per week (end)
beginFavoritesWeeklyNoNumber of new favorites per week (start), which together with the end value form the upstream favorites_weekly

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered externally. The description adds nothing beyond that: no mention of pagination behavior, result limits, credit/quota consumption, or how the many filters combine.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but that brevity is vacuous rather than efficient: the single sentence restates the tool title and delivers no actionable information. Under-specification, not excess length, is the problem.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 28-parameter research query with no output schema, the description should at minimum explain that it returns a filtered, paginated list of Etsy products and what the results represent. Instead it offers only a restated title, leaving the agent to infer everything from the schema and annotations.

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% and all 28 parameters carry their own descriptions, including paired begin/end range semantics and the sortBy/sortDesc encodings. The description contributes nothing further, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description repeats the title verbatim ('Etsy Product Research: etsy/product Query API') without stating a real verb such as search, filter, or list. It only vaguely signals Etsy products as the resource and does nothing to distinguish it from nexscope_etsy_product_detail, nexscope_etsy_store_query, or nexscope_etsy_category_search.

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?

No when-to-use, when-not-to-use, or alternative is named. With 28 optional filters and several nearby Etsy siblings, an agent has no guidance on which tool to pick or what a typical query looks like.

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.