Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

etsy_shop_search

Search Etsy shops by keyword to return shop IDs, names, locations, active listing counts, open dates, and vacation status. Set a limit to control how many shop results you get.

Instructions

Search Etsy shops. Searches Etsy shops by the required keyword q, returning up to limit shops (default 10). Each shop has its id, name, avatar, location, active listing count, open date and a vacation-mode flag.

Input Schema

NameRequiredDescriptionDefault
qYesShop search keyword
limitNoMax shops to return (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 it does enumerate the returned payload (id, name, avatar, location, active listing count, open date, vacation-mode flag), which is genuine value given there is no output schema. It stops short of stating auth needs, rate limits, pagination cursor behavior, or whether `limit` has a maximum.

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?

Three front-loaded sentences that lead with the verb and the return shape. The opening "Search Etsy shops" is immediately restated more fully in the next sentence, which is mild redundancy but not damaging.

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 two-parameter search tool with full schema coverage and no output schema, the description covers the essential gap by listing the returned fields. It is largely complete, with only edge behaviors (pagination, limit ceiling, auth) left open.

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 baseline is 3. The description restates `q` (required keyword) and `limit` (default 10) but adds no syntax, constraints, or format detail beyond what the schema already provides.

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 clear verb+resource ("Search Etsy shops") and specifies the scope as shop-level search keyed by `q`. It implicitly distinguishes from listing-level siblings like etsy_listing/etsy_search, but never names an alternative, so the differentiation is left to inference.

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 shops by the required keyword `q`", which is enough to know broadly what it does. However, it never says when to prefer this over etsy_search, etsy_shop, or etsy_shop_listings, so an agent must infer the routing.

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