Skip to main content
Glama

etsy_search_listings

Read-onlyIdempotent

Search active Etsy listings by keyword and narrow results by price, location, taxonomy, or sort order to identify relevant products for sourcing or market research.

Instructions

Search active Etsy listings by keyword.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api_key": "<api_key>",
      "keywords": "<keywords>"
    },
    "name": "etsy_search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page (max 100, default 25)
offsetNo
api_keyYesEtsy API key
sort_onNoSort field (created, price, score, updated)
keywordsYesSearch keywords
locationNo
max_priceNo
min_priceNo
sort_orderNoasc or desc
taxonomy_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds useful scoping context by stating that only active listings are searched, but it does not discuss pagination, rate limits, or the return format.

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 front-loaded sentence with no wasted words. It is efficient but arguably too sparse for a tool with ten parameters, though conciseness itself is good.

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 ten-parameter search tool with no output schema, the description is incomplete. It omits key behavioral details about filtering options, pagination, authentication requirements beyond the schema's api_key field, and how results are returned.

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 50%, and the description mentions only keyword search, which is already documented in the schema. It does not explain the unpriced parameters such as location, max_price, min_price, taxonomy_id, or offset. The description fails to compensate for the schema gaps.

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?

The description clearly states a specific verb and resource: searching active Etsy listings by keyword. It does not explicitly differentiate from siblings like etsy_search_shops or etsy_get_shop_listings, but the resource and action are unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives such as etsy_search_shops, etsy_get_shop_listings, or etsy_get_listing. It only states what the tool does, leaving all routing decisions to the agent.

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