Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

etsy_search

Search Etsy listings by keyword and page through results to retrieve titles, prices, shop ratings, and stock status for product research or price comparison.

Instructions

Search Etsy listings. Searches Etsy listings across shops for the required keywords q, in Etsy's default relevance order. Page with offset (default 0) and limit (default 36, max 100). The response gives the total match count, and each result has listing id, title, URL, image, price, shop name and rating, quantity and sold-out flag. Read currency, since it is not fixed to USD.

Input Schema

NameRequiredDescriptionDefault
qYesSearch keywords
limitNoPage size (default 36, max 100)
offsetNo0-based result offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the relevance ordering, pagination defaults and max, the total count, result fields, and flags the non-USD currency caveat. It omits auth/permission needs and rate limits, hence not a 5.

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?

Four tight sentences, front-loaded with the core action, then pagination, then return shape, then the currency caveat. Every sentence earns its place and no filler is present.

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?

With no output schema, the description correctly enumerates the return fields and the total count, and warns about currency, which is genuinely necessary for correct interpretation. Only minor gaps remain (no mention of auth or whether the search is anonymous).

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 the schema already documents q, limit, and offset. The description restates the defaults (offset 0, limit 36/max 100) without adding syntax or meaning beyond the schema, which is the baseline-3 case.

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 and resource ('Search Etsy listings') and adds the scope 'across shops', which implicitly differentiates it from shop-scoped siblings like etsy_shop_listings. It does not explicitly name those siblings, so differentiation is only implied.

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 'Search Etsy listings' for a keyword query, but there is no explicit when-to-use, when-not-to-use, or reference to alternatives such as etsy_shop_search or etsy_listing. The agent must infer when this beats the sibling tools.

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