Search Etsy product listings by keyword and retrieve results across shops, with limit and offset controls for pagination.
Search Etsy listings. Returns Etsy product search results across shops for a keyword query.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search keywords | |
| limit | No | Page size (default 36, max 100) | |
| offset | No | 0-based result offset |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states that it returns search results; it does not explain pagination behavior, ordering, authentication requirements, rate limits, or whether results include full listing details. This is a significant gap for a search tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is exactly two short sentences that immediately convey the tool's purpose and scope. There is no redundant or irrelevant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple search tool with no output schema, the description explains the core functionality but omits details about the result structure, pagination behavior, or any constraints. Given the minimal complexity, this is adequate but not comprehensive; an agent may need to inspect actual results to understand the format.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema describes all three parameters with 100% coverage, including types, defaults, and descriptions (e.g., 'Search keywords', 'default 36, max 100'). The description adds no additional parameter-level information, so it meets the baseline but provides no extra value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches Etsy listings and returns results across multiple shops, using a specific verb ('Search') and resource ('Etsy listings'). The phrase 'across shops' distinguishes it from shop-specific tools like etsy_shop_search and etsy_shop_listings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this versus alternatives is provided. The phrase 'across shops' implies it is for general keyword search across the entire marketplace, but it does not mention that shop-specific searches should use etsy_shop_search or that specific listing details should use etsy_listing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.