Skip to main content
Glama

etsy_listing_create

Create a new Etsy listing by providing details like title, description, price, quantity, and category. Supports physical, digital, and custom items with optional shipping and return policies.

Instructions

Create a new listing in a shop

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skusNo
tagsNo
priceYesPrice in shop currency
titleYesListing title
stylesNo
shop_idYes
quantityYesAvailable quantity
who_madeYes
is_supplyNo
materialsNo
when_madeYese.g. 2020_2024, before_2000, etc.
is_taxableNo
item_widthNo
descriptionYesListing description
item_heightNo
item_lengthNo
item_weightNo
taxonomy_idYesEtsy taxonomy/category ID
listing_typeNo
processing_maxNo
processing_minNo
is_customizableNo
shop_section_idNo
item_weight_unitNo
return_policy_idNo
is_personalizableNo
should_auto_renewNo
shipping_profile_idNo
item_dimensions_unitNo
production_partner_idsNo
personalization_is_requiredNo
personalization_instructionsNo
personalization_char_count_maxNo
Behavior1/5

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

No behavioral traits disclosed. Description does not mention idempotency, side effects, error handling, rate limits, or authentication requirements. With no annotations, this leaves agents blind to important behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise but at the cost of informativeness. Four words are insufficient for a tool with 33 parameters. This is under-specification, not efficient conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (33 parameters, no output schema, many siblings), the description is severely incomplete. No mention of return values, side effects, or the Etsy listing creation process.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 18% schema description coverage, the description adds zero meaning to any of the 33 parameters. It does not explain how or why to use parameters like tags, materials, or shipping_profile_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new listing in a shop' clearly states the action (create), the resource (listing), and the location (shop). It is a specific verb-resource pair that distinguishes from related tools like update or delete.

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 on when to use this tool versus alternatives such as etsy_listing_draft_create or etsy_listing_update. Lacks context about prerequisites like needing a shop_id or taxonomy_id from other tools.

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