Skip to main content
Glama

etsy_listings_list

Read-only

List active Etsy listings using filters such as keywords, price range, sorting, and pagination to retrieve specific products from the marketplace.

Instructions

List active Etsy listings with optional filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results (max 100)
offsetNoPagination offset
sort_onNo
keywordsNoSearch keywords
max_priceNo
min_priceNo
sort_orderNo
taxonomy_idNo
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description's 'list' is consistent. It adds that it returns only active listings, but does not disclose other behavioral traits like pagination behavior or rate limits. The description adds some value beyond annotations but not extensively.

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 sentence with no redundancy or filler. However, it is so minimal that it lacks helpful detail, making it slightly under-informative for the number of parameters and siblings.

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?

Given 8 parameters, no output schema, and many sibling tools, the description is incomplete. It omits pagination details, sorting options, and guidance on when to use this versus other listing tools, leaving significant gaps for an agent.

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 38% (3 of 8 parameters have descriptions). The description says 'with optional filters' but does not explain any parameters beyond what's in the schema, so it fails to compensate for the low coverage.

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 it lists 'active Etsy listings' with optional filters, providing a specific verb and resource. However, it does not distinguish this tool from siblings like etsy_listings_search or etsy_listings_list_by_shop, which also list listings.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools that list or search listings, the description lacks any when-to-use or when-not-to-use information.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BusyBee3333/etsy-mcp-2026-complete'

If you have feedback or need assistance with the MCP directory API, please join our Discord server