Skip to main content
Glama
Sign In
etsy-clean-mcp

etsy-clean-mcp

by phobicdotno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

create_draft_listing

Creates an unpublished Etsy draft listing from product details; preview with confirm=false, then submit with confirm=true. Physical items need shipping and readiness IDs for activation.

Instructions

Create a new listing as a DRAFT (never published). confirm=false previews. Physical listings also need shipping_profile_id and readiness_state_id before they can be activated.

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": {
      "title": "<title>",
      "description": "<description>",
      "price": "<price>",
      "quantity": "<quantity>",
      "who_made": "<who_made>",
      "when_made": "<when_made>",
      "taxonomy_id": "<taxonomy_id>"
    },
    "name": "create_draft_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoUp to 13 tags.
typeNo
priceYesPrice in the shop currency, e.g. 24.5.
titleYes
confirmNofalse (default) only returns a preview of the request. true sends it.
quantityYes
who_madeYes
is_supplyNotrue for craft supplies, false for finished products.
materialsNoMaterials (letters, numbers, spaces).
when_madeYes
descriptionYes
taxonomy_idYesSeller taxonomy id (see search_taxonomy).
shop_section_idNoShop section id (see list_shop_sections).
return_policy_idNoReturn policy id (see list_return_policies).
should_auto_renewNo
readiness_state_idNoProcessing profile id (see list_processing_profiles).
shipping_profile_idNoShipping profile id (see list_shipping_profiles).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare the generic profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds genuinely useful behavior beyond that: the created entity is always a draft and never published, confirm=false is a preview rather than a write, and physical listings carry deferred prerequisites checked at activation time. It omits what a preview response contains.

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

Conciseness5/5

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

Three short sentences with zero filler, and the most important constraint (DRAFT, never published) is front-loaded before the preview semantics and prerequisites. Nothing could be removed without losing information.

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 17-parameter mutation tool with no output schema, the description covers the critical decision points: draft-only outcome, preview mode, and activation prerequisites. The main gap is not stating what is returned (a listing id? a preview payload when confirm=false), which matters for chaining into upload_listing_image.

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 coverage is 59% across 17 parameters, so the schema documents a bit over half. The description adds real meaning for two of them by framing shipping_profile_id and readiness_state_id as conditional prerequisites tied to physical listings, but the other 14 parameters (type, tags, materials, return_policy_id, should_auto_renew, etc.) get no clarification beyond the schema.

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 gives a specific verb and resource ('Create a new listing') and adds a hard scope constraint ('as a DRAFT (never published)') that separates it from activate_listing and update_listing. It stops short of naming those siblings explicitly, so an agent must infer the boundary rather than being told it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear conditional guidance: 'confirm=false previews' tells the agent to dry-run first, and the final sentence explains that physical listings will not be activatable without shipping_profile_id and readiness_state_id. No explicit exclusion ('do not use this to modify an existing listing') is stated, which keeps it below a 5.

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