Skip to main content
Glama

commercebridge

by io.github.IsaiahDupree

Search Etsy's site-wide active listings

search_etsy
Read-onlyIdempotent

Search Etsy's site-wide active listings by keyword, built on Etsy's official Open API v3 (app-only, no OAuth). Returns title, description, price, quantity, tags/materials, favorites, images, and shop per listing. Errors honestly until this engine is fully live upstream: currently returns not_found (route not yet redeployed on the production commerce-api), then credentials_required once deployed without ETSY_KEYSTRING/ETSY_SHARED_SECRET provisioned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesKeyword query, e.g. "macrame wall hanging". Required.
limitNoDefault 20. Etsy caps limit at 100.
offsetNoDefault 0.
is_safeNoWhen true, filters out mature/adult content.
sort_onNo
currencyNoISO 4217 code to convert listing prices into.
max_priceNo
min_priceNo
sort_orderNo
taxonomy_idNoEtsy seller-taxonomy category id.
buyer_countryNoISO 3166-1 alpha-2 — filters to listings that ship there.
shop_locationNo

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint), the description adds substantial context: auth model ('app-only, no OAuth'), return fields (title, description, price, etc.), and honest error disclosure ('currently returns not_found... then credentials_required...'). This greatly informs the agent about expected behavior and prerequisites.

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 description is a single, dense paragraph that front-loads the purpose and then provides return fields and error status. The error disclosure is detailed but relevant. It could be split into clearer sentences, but it remains efficient and earns its place.

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 12-parameter search tool with no output schema, the description covers key context: return fields, auth requirements, and error behavior. It lacks explicit pagination semantics and doesn't explain optional filters, but the schema documents several of those. Overall, it provides enough for basic usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 58%, yet the description does not compensate for the gaps. It only implies 'q' via 'by keyword' but leaves parameters like max_price, min_price, shop_location, sort_on, and sort_order unexplained. No additional meaning is provided beyond the sparse schema descriptions.

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?

The description clearly states 'Search Etsy's site-wide active listings by keyword', specifying both the resource (Etsy active listings) and the operation (keyword search). It distinguishes from sibling tools like get_etsy_listing or search_ebay by emphasizing 'site-wide' and 'built on Etsy's official Open API v3'.

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?

The description implies usage for keyword-based site-wide search but does not explicitly state when to use this tool versus alternatives like get_etsy_listing or search_ebay. There are no exclusions or when-not guidance, so the context is clear but not explicit.

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

All commercebridge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools are clearly distinguished by platform and entity (e.g., get_etsy_shop vs get_etsy_listing), but search_shopify and search_shopify_products have overlapping purposes and near-identical names, which could cause misselection. The individual descriptions help, but the boundary is fuzzy.

Naming Consistency4/5

The dominant pattern is get_<platform>_<entity> and search_<platform>_<entity>, which is clear and consistent. However, deviations like search_shopify_products (which lists all products rather than performing a filtered search) and the use of plural get_ebay_items for bulk retrieval break the clean verb_noun convention in a few places.

Tool Count5/5

14 tools across four distinct platforms is well-scoped, with each platform getting a focused set of search and get operations. This is comfortably within the ideal range and each tool serves a concrete purpose.

Completeness4/5

The server provides solid read-only coverage for product search and detail retrieval across four platforms. Minor gaps exist, such as no way to fetch products within a Shopify collection or list Best Buy categories, but these are workaround-able and do not severely impair agent workflows.

Resources